Environment

JDBC autocommit mode

Enable automatic session close at end of transaction

Select a custom batcher.

Should versioned data be included in batching?

Number of connections acquired when pool is exhausted

Idle time before a C3P0 pooled connection is validated

Maximum size of C3P0 connection pool

Maximum size of C3P0 statement cache

Minimum size of C3P0 connection pool

Maximum idle time for C3P0 connection pool

The CacheProvider JNDI namespace, if pre-bound to JNDI.

The CacheProvider implementation class

The CacheProvider implementation class

The RegionFactory implementation class

The CacheProvider region name prefix

Enable nullability checking. Raises an exception if a property marked as not-null is null. Default to false if Bean Validation is present in the classpath and Hibernate Annotations is used, true otherwise.

prefix for arbitrary JDBC connection properties

ConnectionProvider implementor to use when obtaining connections

Context scoping impl for getCurrentSession() processing.

java.sql.Datasource JNDI name

The default batch size for batch fetching

A default database catalog name to use for unqualified tablenames

The EntityMode in which set the Session opened from the SessionFactory.

A default database schema (owner) name to use for unqualified tablenames

Hibernate SQL Dialect class

DialectResolver classes to register with the DialectFactory

JDBC driver class

Enable automatic flush during the JTA beforeCompletion() callback

Enable formatting of SQL logged to the console

Enable statistics collection

Should all database identifiers be quoted.

Auto export/update schema using hbm2ddl tool. Valid values are update, create, create-drop and validate.

Comma-separated names of the optional files containing SQL DML statements executed during the SessionFactory creation. File order matters, the statements of a give file are executed before the statements of the following files. These statements are only executed if the schema is created ie if hibernate.hbm2ddl.auto is set to create or create-drop. The default value is /import.sql

JDBC transaction isolation level

The jacc context id of the deployment

JNDI initial context class, Context.INITIAL_CONTEXT_FACTORY

prefix for arbitrary JNDI InitialContext properties

JNDI provider URL, Context.PROVIDER_URL

Maximum depth of outer join fetching

Enable ordering of insert statements for the purpose of more efficient JDBC batching.

Enable ordering of update statements by primary key value

An XSLT resource used to generate "custom" XML

JDBC password

Maximum number of inactive connections for Hibernate's connection pool

When using pooled optimizers, prefer interpreting the database value as the lower (lo) boundary. The default is to interpret it as the high boundary.

Proxool property to configure the Proxool Provider from an already existing pool (true / false)

Proxool property with the Proxool pool alias to use (Required for PROXOOL_EXISTING_POOL, PROXOOL_PROPERTIES, or PROXOOL_XML)

Proxool/Hibernate property prefix

Proxool property to configure the Proxool Provider using a properties file (/path/to/proxool.properties)

Proxool property to configure the Proxool Provider using an XML (/path/to/file.xml)

The QueryCacheFactory implementation class.

The maximum number of soft references maintained by SoftLimitMRUCache. Default is 2048.

The maximum number of strong references maintained by SoftLimitMRUCache. Default is 128.

Should named queries be checked during startup (the default is enabled).

Mainly intended for test environments.

A comma-separated list of token substitutions to use when translating a Hibernate query to SQL

The classname of the HQL query parser factory

Specifies how Hibernate should release JDBC connections.

JNDI name to bind to SessionFactory

Enable logging of generated SQL to the console

The SQLExceptionConverter to use for converting SQLExceptions to Hibernate's JDBCException hierarchy. The default is to use the configured Dialect's preferred SQLExceptionConverter.

Maximum JDBC batch size. A nonzero value enables batch updates.

Gives the JDBC driver a hint as to the number of rows that should be fetched from the database when more rows are needed. If 0, JDBC driver default settings will be used.

TransactionManagerLookup implementor to use for obtaining the TransactionManager

TransactionFactory implementor to use for creating Transactions

JDBC URL

JDBC user

JNDI name of JTA UserTransaction object

Tells the JDBC driver to attempt to retrieve row Id with the JDBC 3.0 PreparedStatement.getGeneratedKeys() method. In general, performance will be better if this property is set to true and the underlying JDBC driver supports getGeneratedKeys().

Optimize the cache for minimal puts instead of minimal gets

Enable the query cache (disabled by default)

Use bytecode libraries optimized property access

Use JDBC scrollable ResultSets. This property is only necessary when there is no ConnectionProvider, ie. the user is supplying JDBC connections.

Enable the second-level cache (enabled by default)

Add comments to the generated SQL

Use java.io streams to read / write binary data from / to JDBC

Enable use of structured second-level cache entries

Enable wrapping of JDBC result sets in order to speed up column name lookups for broken JDBC drivers

Return System properties, extended by any properties specified in hibernate.properties.

Get the name of a JDBC transaction isolation level

Does this JVM handle java.sql.Timestamp in the JDK 1.4 compliant way wrt to nano rolling>

Does this JVM's implementation of java.sql.Timestamp have a bug in which the following is true: new java.sql.Timestamp( x ).getTime() != x

NOTE : IBM JDK 1.3.1 the only known JVM to exhibit this behavior.

Does this JDK/JVM define the JDBC Statement interface with a 'getGeneratedKeys' method?

Note, this is true for JDK 1.4 and above; hence the deprecation.

Does this JVM support LinkedHashSet and LinkedHashMap?

Note, this is true for JDK 1.4 and above; hence the deprecation.

Should we use reflection optimization?

Should we use streams to bind binary types to JDBC IN parameters?

Issues warnings to the user when any obsolete or renamed property names are used.