hibernate 可选配置

Hibernate Configuration Properties

Property namePurposehibernate.dialectThe classname of a Hibernateorg.hibernate.dialect.Dialect which allows Hibernate to generate SQL optimized for a particular relational database.

e.g. full.classname.of.Dialect

In most cases Hibernate will actually be able to choose the correct org.hibernate.dialect.Dialect implementation based on the JDBC metadata returned by the JDBC driver.

hibernate.show_sqlWrite all SQL statements to console. This is an alternative to setting the log category org.hibernate.SQL to debug.

e.g. true | false

hibernate.format_sqlPretty print the SQL in the log and console. 

e.g. true | false

hibernate.default_schemaQualify unqualified table names with the given schema/tablespace in generated SQL. 

e.g. SCHEMA_NAME

hibernate.default_catalogQualifies unqualified table names with the given catalog in generated SQL. 

e.g. CATALOG_NAME

hibernate.session_factory_nameThe org.hibernate.SessionFactory will be automatically bound to this name in JNDI after it has been created.

e.g. jndi/composite/name

hibernate.max_fetch_depthSets a maximum "depth" for the outer join fetch tree for single-ended associations (one-to-one, many-to-one). A 0disables default outer join fetching.

e.g. recommended values between 0 and 3

hibernate.default_batch_fetch_sizeSets a default size for Hibernate batch fetching of associations. 

e.g. recommended values 4, 8, 16

hibernate.default_entity_modeSets a default mode for entity representation for all sessions opened from this SessionFactory, defaults to pojo.

e.g. dynamic-map | pojo

hibernate.order_updatesForces Hibernate to order SQL updates by the primary key value of the items being updated. This will result in fewer transaction deadlocks in highly concurrent systems. 

e.g. true| false

hibernate.generate_statisticsIf enabled, Hibernate will collect statistics useful for performance tuning. 

e.g. true | false

hibernate.use_identifier_rollbackIf enabled, generated identifier properties will be reset to default values when objects are deleted. 

e.g. true | false

hibernate.use_sql_commentsIf turned on, Hibernate will generate comments inside the SQL, for easier debugging, defaults to false.

e.g. true | false

hibernate.id.new_generator_mappingsSetting is relevant when using @GeneratedValue. It indicates whether or not the new IdentifierGeneratorimplementations are used forjavax.persistence.GenerationType.AUTO,javax.persistence.GenerationType.TABLE andjavax.persistence.GenerationType.SEQUENCE. Default tofalse to keep backward compatibility.

e.g. true | false

 Hibernate JDBC and Connection Properties

Property namePurposehibernate.jdbc.fetch_sizeA non-zero value determines the JDBC fetch size (callsStatement.setFetchSize()).hibernate.jdbc.batch_sizeA non-zero value enables use of JDBC2 batch updates by Hibernate. 

e.g. recommended values between 5 and 30

hibernate.jdbc.batch_versioned_dataSet this property to true if your JDBC driver returns correct row counts from executeBatch(). It is usually safe to turn this option on. Hibernate will then use batched DML for automatically versioned data. Defaults to false.

e.g. true | false

hibernate.jdbc.factory_classSelect a custom org.hibernate.jdbc.Batcher. Most applications will not need this configuration property.

e.g. classname.of.BatcherFactory

hibernate.jdbc.use_scrollable_resultsetEnables use of JDBC2 scrollable resultsets by Hibernate. This property is only necessary when using user-supplied JDBC connections. Hibernate uses connection metadata otherwise. 

e.g. true | false

hibernate.jdbc.use_streams_for_binaryUse streams when writing/reading binary or serializabletypes to/from JDBC. *system-level property*

e.g. true | false

hibernate.jdbc.use_get_generated_keysEnables use of JDBC3PreparedStatement.getGeneratedKeys() to retrieve natively generated keys after insert. Requires JDBC3+ driver and JRE1.4+, set to false if your driver has problems with the Hibernate identifier generators. By default, it tries to determine the driver capabilities using connection metadata.

e.g. true|false

hibernate.connection.provider_classThe classname of a customorg.hibernate.connection.ConnectionProvider which provides JDBC connections to Hibernate.

e.g. classname.of.ConnectionProvider

hibernate.connection.isolationSets the JDBC transaction isolation level. Checkjava.sql.Connection for meaningful values, but note that most databases do not support all isolation levels and some define additional, non-standard isolations.

e.g. 1, 2, 4, 8

hibernate.connection.autocommitEnables autocommit for JDBC pooled connections (it is not recommended). 

e.g. true | false

hibernate.connection.release_modeSpecifies when Hibernate should release JDBC connections. By default, a JDBC connection is held until the session is explicitly closed or disconnected. For an application server JTA datasource, use after_statement to aggressively release connections after every JDBC call. For a non-JTA connection, it often makes sense to release the connection at the end of each transaction, by usingafter_transaction. auto will choose after_statement for the JTA and CMT transaction strategies andafter_transaction for the JDBC transaction strategy.

e.g. auto (default) | on_close | after_transaction |after_statement

This setting only affects Sessions returned fromSessionFactory.openSession. For Sessions obtained through SessionFactory.getCurrentSession, theCurrentSessionContext implementation configured for use controls the connection release mode for those Sessions. See Section 2.2, “Contextual sessions”

hibernate.connection.<propertyName>Pass the JDBC property <propertyName> toDriverManager.getConnection().hibernate.jndi.<propertyName>Pass the property <propertyName> to the JNDIInitialContextFactory.

Hibernate Cache Properties

Property namePurposehibernate.cache.provider_classThe classname of a custom CacheProvider.

e.g. classname.of.CacheProvider

hibernate.cache.use_minimal_putsOptimizes second-level cache operation to minimize writes, at the cost of more frequent reads. This setting is most useful for clustered caches and, in Hibernate, is enabled by default for clustered cache implementations. 

e.g. true|false

hibernate.cache.use_query_cacheEnables the query cache. Individual queries still have to be set cachable. 

e.g. true|false

hibernate.cache.use_second_level_cacheCan be used to completely disable the second level cache, which is enabled by default for classes which specify a <cache> mapping.

e.g. true|false

hibernate.cache.query_cache_factoryThe classname of a custom QueryCache interface, defaults to the built-in StandardQueryCache.

e.g. classname.of.QueryCache

hibernate.cache.region_prefixA prefix to use for second-level cache region names.

e.g. prefix

hibernate.cache.use_structured_entriesForces Hibernate to store data in the second-level cache in a more human-friendly format. 

e.g. true|false

hibernate.cache.auto_evict_collection_cacheEnables the automatic eviction of a bi-directional association's collection cache when an element in the ManyToOne collection is added/updated/removed without properly managing the change on the OneToMany side. 

e.g. true|false (default: false)

hibernate.cache.default_cache_concurrency_strategySetting used to give the name of the defaultorg.hibernate.annotations.CacheConcurrencyStrategyto use when either @Cacheable or @Cache is used.@Cache(strategy="..") is used to override this default.

Hibernate Transaction Properties

Property namePurposehibernate.transaction.factory_classThe classname of a TransactionFactory to use with Hibernate Transaction API (defaults toJDBCTransactionFactory).

e.g. classname.of.TransactionFactory

jta.UserTransactionA JNDI name used by JTATransactionFactory to obtain the JTA UserTransaction from the application server.

e.g. jndi/composite/name

hibernate.transaction.manager_lookup_classThe classname of a TransactionManagerLookup. It is required when JVM-level caching is enabled or when using hilo generator in a JTA environment.

e.g. classname.of.TransactionManagerLookup

hibernate.transaction.flush_before_completionIf enabled, the session will be automatically flushed during the before completion phase of the transaction. Built-in and automatic session context management is preferred, see Section 2.2, “Contextual sessions”.

e.g. true | false

hibernate.transaction.auto_close_sessionIf enabled, the session will be automatically closed during the after completion phase of the transaction. Built-in and automatic session context management is preferred, see Section 2.2, “Contextual sessions”.

e.g. true | false

Miscellaneous Properties

Property namePurposehibernate.current_session_context_classSupply a custom strategy for the scoping of the "current" Session. SeeSection 2.2, “Contextual sessions” for more information about the built-in strategies.

e.g. jta | thread | managed | custom.Class

hibernate.query.factory_classChooses the HQL parser implementation. 

e.g.org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory ororg.hibernate.hql.internal.classic.ClassicQueryTranslatorFactory

hibernate.query.substitutionsIs used to map from tokens in Hibernate queries to SQL tokens (tokens might be function or literal names, for example). 

e.g.hqlLiteral=SQL_LITERAL, hqlFunction=SQLFUNC

hibernate.hbm2ddl.autoAutomatically validates or exports schema DDL to the database when the SessionFactory is created. With create-drop, the database schema will be dropped when the SessionFactory is closed explicitly.

e.g. validate | update | create | create-drop

hibernate.hbm2ddl.import_files

Comma-separated names of the optional files containing SQL DML statements executed during the SessionFactory creation. This is useful for testing or demoing: by adding INSERT statements for example you can populate your database with a minimal set of data when it is deployed.

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.

e.g. /humans.sql,/dogs.sql

hibernate.hbm2ddl.import_files_sql_extractor

The classname of a custom ImportSqlCommandExtractor (defaults to the built-in SingleLineSqlCommandExtractor). This is useful for implementing dedicated parser that extracts single SQL statements from each import file. Hibernate provides alsoMultipleLinesSqlCommandExtractor which supports instructions/comments and quoted strings spread over multiple lines (mandatory semicolon at the end of each statement).

e.g. classname.of.ImportSqlCommandExtractor

hibernate.bytecode.use_reflection_optimizer

Enables the use of bytecode manipulation instead of runtime reflection. This is a System-level property and cannot be set inhibernate.cfg.xml. Reflection can sometimes be useful when troubleshooting. Hibernate always requires javassist even if you turn off the optimizer.

e.g. true | false

hibernate.bytecode.provider

At the moment, javassist is the only supported bytecode provider.

e.g. javassist