All Known Implementing Classes:

Environment
```
public interface AvailableSettings
```
Enumerates the configuration properties supported by Hibernate, including properties defined by the JPA specification.

Field Summary

Fields
Modifier and Type	Field	Description
`static String`	`ALLOW_JTA_TRANSACTION_ACCESS`	When enabled, allows access to the `Transaction` even when using a JTA for transaction management.
`static String`	`ALLOW_REFRESH_DETACHED_ENTITY`	When enabled, allows calls to `EntityManager.refresh(Object)` and `Session.refresh(Object)` on a detached entity instance.
`static String`	`ALLOW_UPDATE_OUTSIDE_TRANSACTION`	When enabled, allows update operations outside a transaction.
`static String`	`ARTIFACT_PROCESSING_ORDER`	Specifies the order in which metadata sources should be processed, is a delimited list of values defined by `MetadataSourceType`.
`static String`	`AUTO_CLOSE_SESSION`	When enabled, specifies that the `Session` should be closed automatically at the end of each transaction.
`static String`	`AUTO_EVICT_COLLECTION_CACHE`	Enables the automatic eviction of a bidirectional association's collection cache when an element in the `ManyToOne` collection is added, updated, or removed without properly managing the change on the `OneToMany` side.
`static String`	`AUTO_SESSION_EVENTS_LISTENER`	Defines a default `SessionEventListener` to be applied to newly-opened `Session`s.
`static String`	`AUTOCOMMIT`	Controls the autocommit mode of JDBC connections obtained from any `ConnectionProvider` implementation which respects this setting, which the built-in implementations do, except for `DatasourceConnectionProviderImpl`.
`static String`	`BATCH_FETCH_STYLE`	Deprecated. An appropriate batch-fetch style is selected automatically
`static String`	`BATCH_STRATEGY`	Specifies a custom `BatchBuilder`.
`static String`	`BATCH_VERSIONED_DATA`	When enabled, specifies that `versioned` data should be included in batching.
`static String`	`BEAN_CONTAINER`	Identifies a `BeanContainer` to be used.
`static String`	`BYTECODE_PROVIDER`	Selects a bytecode enhancment library.
`static String`	`C3P0_ACQUIRE_INCREMENT`	Number of connections acquired when pool is exhausted
`static String`	`C3P0_CONFIG_PREFIX`	A setting prefix used to indicate settings that target the hibernate-c3p0 integration
`static String`	`C3P0_IDLE_TEST_PERIOD`	Idle time before a C3P0 pooled connection is validated
`static String`	`C3P0_MAX_SIZE`	Maximum size of C3P0 connection pool
`static String`	`C3P0_MAX_STATEMENTS`	Maximum size of C3P0 statement cache
`static String`	`C3P0_MIN_SIZE`	Minimum size of C3P0 connection pool
`static String`	`C3P0_TIMEOUT`	Maximum idle time for C3P0 connection pool
`static String`	`CACHE_KEYS_FACTORY`	Deprecated. this is only honored for hibernate-infinispan
`static String`	`CACHE_REGION_FACTORY`	The `RegionFactory` implementation, either: an instance of `RegionFactory`, a `Class` implementing `RegionFactory`, or he name of a class implementing `RegionFactory`.
`static String`	`CACHE_REGION_PREFIX`	The `CacheProvider` region name prefix
`static String`	`CALLABLE_NAMED_PARAMS_ENABLED`	When enabled, specifies that Hibernate should attempt to map parameter names given in a `ProcedureCall` or `StoredProcedureQuery` to named parameters of the JDBC `CallableStatement`.
`static String`	`CDI_BEAN_MANAGER`	Deprecated.
`static String`	`CFG_XML_FILE`
`static String`	`CHECK_NULLABILITY`	Enable nullability checking, raises an exception if an attribute marked as not null is null at runtime.
`static String`	`CLASS_CACHE_PREFIX`	Entity cache configuration properties follow the pattern `hibernate.classcache.packagename.ClassName usage[, region]` where `usage` is the cache strategy used and `region` the cache region name
`static String`	`CLASSLOADERS`	Specifies a `collection` of the `ClassLoader` instances Hibernate should use for classloading and resource loading.
`static String`	`COLLECTION_CACHE_PREFIX`	Collection cache configuration properties follow the pattern `hibernate.collectioncache.packagename.ClassName.role usage[, region]` where `usage` is the cache strategy used and `region` the cache region name
`static String`	`CONNECTION_HANDLING`	Specifies how Hibernate should manage JDBC connections in terms of acquisition and release.
`static String`	`CONNECTION_PREFIX`	A prefix for properties specifying arbitrary JDBC connection properties.
`static String`	`CONNECTION_PROVIDER`	Specifies a `ConnectionProvider` to use for obtaining JDBC connections, either: an instance of `ConnectionProvider`, a `Class` representing a class that implements `ConnectionProvider`, or the name of a class that implements `ConnectionProvider`.
`static String`	`CONNECTION_PROVIDER_DISABLES_AUTOCOMMIT`	Allows a user to tell Hibernate that the connections we obtain from the configured `ConnectionProvider` will already have autocommit disabled when we acquire them from the provider.
`static String`	`CREATE_EMPTY_COMPOSITES_ENABLED`	[EXPERIMENTAL] Enable instantiation of composite/embedded objects when all attribute values are `null`.
`static String`	`CRITERIA_VALUE_HANDLING_MODE`	By default, criteria queries use bind parameters for any value passed via the JPA Criteria API.
`static String`	`CURRENT_SESSION_CONTEXT_CLASS`	Specifies a `CurrentSessionContext` for scoping the current session.
`static String`	`CUSTOM_ENTITY_DIRTINESS_STRATEGY`	Setting to identify a `CustomEntityDirtinessStrategy` to use.
`static String`	`DATASOURCE`	Specifies a `DataSource`, either: an instance of `DataSource`, or a JNDI name under which to obtain the `DataSource`.
`static String`	`DEFAULT_BATCH_FETCH_SIZE`	Specifies the default batch size for batch fetching.
`static String`	`DEFAULT_CACHE_CONCURRENCY_STRATEGY`	Specifies the `CacheConcurrencyStrategy` to use by default when an entity is marked `@Cacheable`, but no concurrency strategy is explicitly specified via the `Cache` annotation.
`static String`	`DEFAULT_CATALOG`	A default database catalog name to use for unqualified table names
`static String`	`DEFAULT_LIST_SEMANTICS`	Specifies the `CollectionClassification` to use when Hibernate detects a plural attribute typed as `List` with no explicit list index configuration.
`static String`	`DEFAULT_NULL_ORDERING`	Default precedence of null values in `ORDER BY` clause.
`static String`	`DEFAULT_SCHEMA`	A default database schema (owner) name to use for unqualified table names
`static String`	`DELAY_CDI_ACCESS`	Used in conjunction with "hibernate.resource.beans.container" when CDI is used.
`static String`	`DELAY_ENTITY_LOADER_CREATIONS`	Controls how entity loaders are created.
`static String`	`DIALECT`	Specifies the Hibernate SQL `Dialect` class.
`static String`	`DIALECT_DB_MAJOR_VERSION`	Deprecated. Use `JAKARTA_HBM2DDL_DB_MAJOR_VERSION` instead
`static String`	`DIALECT_DB_MINOR_VERSION`	Deprecated. Use `JAKARTA_HBM2DDL_DB_MINOR_VERSION` instead
`static String`	`DIALECT_DB_NAME`	Deprecated. Use `JAKARTA_HBM2DDL_DB_NAME` instead
`static String`	`DIALECT_DB_VERSION`	Deprecated. Use `JAKARTA_HBM2DDL_DB_VERSION` instead
`static String`	`DIALECT_RESOLVERS`	Specifies additional `DialectResolver` implementations to register with the standard `DialectFactory`.
`static String`	`DISCARD_PC_ON_CLOSE`	When enabled, specifies that the persistent context should be discarded when either `SharedSessionContract.close()` or `EntityManager.close()` is called.
`static String`	`DRIVER`	Specifies the JDBC driver class.
`static String`	`ENABLE_LAZY_LOAD_NO_TRANS`
`static String`	`ENABLE_SYNONYMS`	If enabled, allows schema update and validation to support synonyms.
`static String`	`ENHANCER_ENABLE_ASSOCIATION_MANAGEMENT`	Enable association management feature in runtime bytecode enhancement
`static String`	`ENHANCER_ENABLE_DIRTY_TRACKING`	Enable dirty tracking feature in runtime bytecode enhancement
`static String`	`ENHANCER_ENABLE_LAZY_INITIALIZATION`	Enable lazy loading feature in runtime bytecode enhancement
`static String`	`EVENT_LISTENER_PREFIX`	Event listener configuration properties follow the pattern `hibernate.event.listener.eventType packageName.ClassName1, packageName.ClassName2`
`static String`	`EXTRA_PHYSICAL_TABLE_TYPES`	Specifies a comma-separated list of extra table types, in addition to the default types `"TABLE"` and `"VIEW"`, to recognize as physical tables when performing schema update, creation and validation.
`static String`	`FAIL_ON_PAGINATION_OVER_COLLECTION_FETCH`	When pagination is used in combination with a `fetch join` applied to a collection or many-valued association, the limit must be applied in-memory instead of on the database.
`static String`	`FLUSH_BEFORE_COMPLETION`	When enabled, specifies that automatic flushing should occur during the JTA `Synchronization.beforeCompletion()` callback.
`static String`	`FLUSH_MODE`	Used to determine flush mode.
`static String`	`FORCE_DISCRIMINATOR_IN_SELECTS_BY_DEFAULT`
`static String`	`FORMAT_SQL`	Enables formatting of SQL logged to the console.
`static String`	`GENERATE_STATISTICS`	When enabled, specifies that statistics should be collected.
`static String`	`GLOBALLY_QUOTED_IDENTIFIERS`	When enabled, all database identifiers are quoted.
`static String`	`GLOBALLY_QUOTED_IDENTIFIERS_SKIP_COLUMN_DEFINITIONS`	Assuming `GLOBALLY_QUOTED_IDENTIFIERS`, this allows global quoting to skip column definitions defined by `Column`, `JoinColumn`, etc.
`static String`	`HBM_XML_FILES`
`static String`	`HBM2DDL_AUTO`	Setting to perform `SchemaManagementTool` actions automatically as part of the `SessionFactory` lifecycle.
`static String`	`HBM2DDL_CHARSET_NAME`	The name of the charset used by the schema generation resource.
`static String`	`HBM2DDL_CONNECTION`	Deprecated. Use `JAKARTA_HBM2DDL_CONNECTION` instead
`static String`	`HBM2DDL_CREATE_NAMESPACES`	Specifies whether to automatically create also the database schema/catalog.
`static String`	`HBM2DDL_CREATE_SCHEMAS`	Deprecated. Use `JAKARTA_HBM2DDL_CREATE_SCHEMAS` instead
`static String`	`HBM2DDL_CREATE_SCRIPT_SOURCE`	Specifies the CREATE script file as either a `Reader` configured for reading the DDL script file or a string designating a file `URL` for the DDL script.
`static String`	`HBM2DDL_CREATE_SOURCE`	Specifies whether schema generation commands for schema creation are to be determined based on object/relational mapping metadata, DDL scripts, or a combination of the two.
`static String`	`HBM2DDL_DATABASE_ACTION`	Deprecated. Use `JAKARTA_HBM2DDL_SCRIPTS_ACTION` instead
`static String`	`HBM2DDL_DEFAULT_CONSTRAINT_MODE`	Used with the `ConstraintMode.PROVIDER_DEFAULT` strategy for foreign key mapping.
`static String`	`HBM2DDL_DELIMITER`	Identifies the delimiter to use to separate schema management statements in script outputs.
`static String`	`HBM2DDL_DROP_SCRIPT_SOURCE`	Specifies the DROP script file as either a `Reader` configured for reading the DDL script file or a string designating a file `URL` for the DDL script.
`static String`	`HBM2DDL_DROP_SOURCE`	Specifies whether schema generation commands for schema dropping are to be determined based on object/relational mapping metadata, DDL scripts, or a combination of the two.
`static String`	`HBM2DDL_FILTER_PROVIDER`	Used to specify the `SchemaFilterProvider` to be used by create, drop, migrate and validate operations on the database schema.
`static String`	`HBM2DDL_HALT_ON_ERROR`	When enabled, specifies that the schema migration tool should halt on any error, terminating the bootstrap process.
`static String`	`HBM2DDL_IMPORT_FILES`	Specifies a comma-separated list of file names of scripts containing SQL DML statements that should be executed after schema export completes.
`static String`	`HBM2DDL_IMPORT_FILES_SQL_EXTRACTOR`	Reference to the `SqlScriptCommandExtractor` implementation class to use for parsing source/import files as defined by `HBM2DDL_CREATE_SCRIPT_SOURCE`, `HBM2DDL_DROP_SCRIPT_SOURCE` or `HBM2DDL_IMPORT_FILES`.
`static String`	`HBM2DDL_JDBC_METADATA_EXTRACTOR_STRATEGY`	Setting to choose the strategy used to access the JDBC Metadata.
`static String`	`HBM2DDL_LOAD_SCRIPT_SOURCE`	Deprecated. Use `JAKARTA_HBM2DDL_LOAD_SCRIPT_SOURCE` instead
`static String`	`HBM2DDL_SCRIPTS_ACTION`	Deprecated. Use `JAKARTA_HBM2DDL_SCRIPTS_ACTION` instead
`static String`	`HBM2DDL_SCRIPTS_CREATE_APPEND`	For cases where the "javax.persistence.schema-generation.scripts.action" value indicates that schema commands should be written to DDL script file, specifies if schema commands should be appended to the end of the file rather than written at the beginning of the file.
`static String`	`HBM2DDL_SCRIPTS_CREATE_TARGET`	For cases where the "javax.persistence.schema-generation.scripts.action" value indicates that schema creation commands should be written to DDL script file, "javax.persistence.schema-generation.scripts.create-target" specifies either a `Writer` configured for output of the DDL script or a string specifying the file URL for the DDL script.
`static String`	`HBM2DDL_SCRIPTS_DROP_TARGET`	For cases where the "javax.persistence.schema-generation.scripts.action" value indicates that schema drop commands should be written to DDL script file, "javax.persistence.schema-generation.scripts.drop-target" specifies either a `Writer` configured for output of the DDL script or a string specifying the file URL for the DDL script.
`static String`	`HIGHLIGHT_SQL`	Enables highlighting of SQL logged to the console using ANSI escape codes.
`static String`	`IDENTIFIER_GENERATOR_STRATEGY_PROVIDER`	Deprecated. use `GenerationTypeStrategyRegistration` instead
`static String`	`IGNORE_EXPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS`	The legacy behavior of Hibernate is to not use discriminators for joined inheritance (Hibernate does not need the discriminator).
`static String`	`IMMUTABLE_ENTITY_UPDATE_QUERY_HANDLING_MODE`	This setting defines how `Immutable` entities are handled when executing a bulk update query.
`static String`	`IMPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS`	The legacy behavior of Hibernate is to not use discriminators for joined inheritance (Hibernate does not need the discriminator.).
`static String`	`IMPLICIT_NAMING_STRATEGY`	Used to specify the `ImplicitNamingStrategy` class to use.
`static String`	`IN_CLAUSE_PARAMETER_PADDING`	Determines how parameters occurring in a SQL `IN` predicate are expanded.
`static String`	`INTERCEPTOR`	Specifies an `Interceptor` implementation associated with the `SessionFactory` and propagated to each `Session` created from the `SessionFactory`.
`static String`	`ISOLATION`	Specified the JDBC transaction isolation level.
`static String`	`JAKARTA_CDI_BEAN_MANAGER`	Used to pass a CDI `BeanManager` to Hibernate.
`static String`	`JAKARTA_HBM2DDL_CONNECTION`	Allows passing a specific `Connection` instance to be used by `SchemaManagementTool` for the purpose of determining the `Dialect`, and for performing {@value #JAKARTA_HBM2DDL_DATABASE_ACTION database actions} if requested.
`static String`	`JAKARTA_HBM2DDL_CREATE_SCHEMAS`	The JPA variant of `HBM2DDL_CREATE_NAMESPACES` used to specify whether database schemas used in the mapping model should be created on export in addition to creating the tables, sequences, etc.
`static String`	`JAKARTA_HBM2DDL_CREATE_SCRIPT_SOURCE`	Specifies the CREATE script file as either a `Reader` configured for reading the DDL script file or a string designating a file `URL` for the DDL script.
`static String`	`JAKARTA_HBM2DDL_CREATE_SOURCE`	Specifies whether schema generation commands for schema creation are to be determined based on object/relational mapping metadata, DDL scripts, or a combination of the two.
`static String`	`JAKARTA_HBM2DDL_DATABASE_ACTION`	Specifies what type of schema tooling action should be performed against the database specified using either "jakarta.persistence.schema-generation-connection" or the configured `ConnectionProvider` for the `SessionFactory`.
`static String`	`JAKARTA_HBM2DDL_DB_MAJOR_VERSION`	Used in conjunction with "jakarta.persistence.database-product-name" for the purpose of determining the `Dialect` to use when the name does not provide enough detail.
`static String`	`JAKARTA_HBM2DDL_DB_MINOR_VERSION`	Used in conjunction with "jakarta.persistence.database-product-name" for the purpose of determining the `Dialect` to use when the name does not provide enough detail.
`static String`	`JAKARTA_HBM2DDL_DB_NAME`	Specifies the name of the database vendor (as would be reported by `DatabaseMetaData.getDatabaseProductName()`) for the purpose of determining the `Dialect` to use.
`static String`	`JAKARTA_HBM2DDL_DB_VERSION`	Used in conjunction with "jakarta.persistence.database-product-name" for the purpose of determining the `Dialect` to use when the name does not provide enough detail.
`static String`	`JAKARTA_HBM2DDL_DROP_SCRIPT_SOURCE`	Specifies the DROP script file as either a `Reader` configured for reading the DDL script file or a string designating a file `URL` for the DDL script.
`static String`	`JAKARTA_HBM2DDL_DROP_SOURCE`	Specifies whether schema generation commands for schema dropping are to be determined based on object/relational mapping metadata, DDL scripts, or a combination of the two.
`static String`	`JAKARTA_HBM2DDL_LOAD_SCRIPT_SOURCE`	JPA-standard variant of `HBM2DDL_IMPORT_FILES` for specifying a database initialization script to be run as part of schema-export Specifies a `Reader` configured for reading of the SQL load script or a string designating the `URL` for the SQL load script.
`static String`	`JAKARTA_HBM2DDL_SCRIPTS_ACTION`	Specifies what type of schema tooling action should be written to script files.
`static String`	`JAKARTA_HBM2DDL_SCRIPTS_CREATE_TARGET`	For cases where "jakarta.persistence.schema-generation.scripts.action" indicates that schema creation commands should be written to a script file, this setting specifies either a `Writer` configured for output of the DDL script or a string specifying the file URL for the DDL script.
`static String`	`JAKARTA_HBM2DDL_SCRIPTS_DROP_TARGET`	For cases where "jakarta.persistence.schema-generation.scripts.action" indicates that schema drop commands should be written to a script file, this setting specifies either a `Writer` configured for output of the DDL script or a string specifying the file URL for the DDL script.
`static String`	`JAKARTA_JDBC_DRIVER`	Specifies the name of a JDBC driver to use to connect to the database.
`static String`	`JAKARTA_JDBC_PASSWORD`	Specifies the password to use when connecting via JDBC.
`static String`	`JAKARTA_JDBC_URL`	Specifies the JDBC connection URL to use to connect to the database.
`static String`	`JAKARTA_JDBC_USER`	Specifies the database user to use when connecting via JDBC.
`static String`	`JAKARTA_JTA_DATASOURCE`	Specifies the JNDI name of a JTA `DataSource`.
`static String`	`JAKARTA_LOCK_SCOPE`	Used to request (hint) a pessimistic lock scope.
`static String`	`JAKARTA_LOCK_TIMEOUT`	Used to request (hint) a pessimistic lock timeout in milliseconds.
`static String`	`JAKARTA_NON_JTA_DATASOURCE`	Specifies the JNDI name of a non-JTA `DataSource`.
`static String`	`JAKARTA_PERSIST_VALIDATION_GROUP`	Used to coordinate with bean validators.
`static String`	`JAKARTA_PERSISTENCE_PROVIDER`	Specifies a class implementing `PersistenceProvider`.
`static String`	`JAKARTA_REMOVE_VALIDATION_GROUP`	Used to coordinate with bean validators.
`static String`	`JAKARTA_SHARED_CACHE_MODE`	When enabled, specifies that the second-level cache (which JPA calls the "shared" cache) may be used, as per the rules defined in JPA 2 section 3.1.7.
`static String`	`JAKARTA_SHARED_CACHE_RETRIEVE_MODE`
`static String`	`JAKARTA_SHARED_CACHE_STORE_MODE`
`static String`	`JAKARTA_TRANSACTION_TYPE`	Specifies the type of transactions supported by the entity managers.
`static String`	`JAKARTA_UPDATE_VALIDATION_GROUP`	Used to coordinate with bean validators.
`static String`	`JAKARTA_VALIDATION_FACTORY`	Used to pass along any discovered `ValidatorFactory`.
`static String`	`JAKARTA_VALIDATION_MODE`	Indicates which form of automatic validation is in effect as per the rules defined in JPA 2 section 3.6.1.1.
`static String`	`JDBC_TIME_ZONE`	Specify a time zone that should be passed to `PreparedStatement.setTimestamp(int, java.sql.Timestamp, java.util.Calendar)` and `PreparedStatement.setTime(int, java.sql.Time, java.util.Calendar)` when binding parameters.
`static String`	`JNDI_CLASS`	Specifies the JNDI `InitialContext` implementation class.
`static String`	`JNDI_PREFIX`	A prefix for properties specifying arbitrary JNDI `InitialContext` properties.
`static String`	`JNDI_URL`	Specifies the JNDI provider/connection URL.
`static String`	`JPA_CACHING_COMPLIANCE`	By default, Hibernate uses second-level cache invalidation for entities with secondary tables in order to avoid the possibility of inconsistent cached data in the case where different transactions simultaneously update different table rows corresponding to the same entity instance.
`static String`	`JPA_CALLBACKS_ENABLED`	JPA callbacks are enabled by default.
`static String`	`JPA_CLOSED_COMPLIANCE`	JPA specifies that an `IllegalStateException` must be thrown by `EntityManager.close()` and `EntityManagerFactory.close()` if the object has already been closed.
`static String`	`JPA_COMPLIANCE`	Specifies a default value for all `JpaCompliance` flags.
`static String`	`JPA_ID_GENERATOR_GLOBAL_SCOPE_COMPLIANCE`	Determines whether the scope of any identifier generator name specified via `TableGenerator.name()` or `SequenceGenerator.name()` is considered global to the persistence unit, or local to the entity in which identifier generator is defined.
`static String`	`JPA_JDBC_DRIVER`	Deprecated. Use `JAKARTA_JDBC_DRIVER` instead
`static String`	`JPA_JDBC_PASSWORD`	Deprecated. Use `JAKARTA_JDBC_PASSWORD` instead
`static String`	`JPA_JDBC_URL`	Deprecated. Use `JAKARTA_JDBC_URL` instead
`static String`	`JPA_JDBC_USER`	Deprecated. Use `JAKARTA_JDBC_USER` instead
`static String`	`JPA_JTA_DATASOURCE`	Deprecated. Use `JAKARTA_JTA_DATASOURCE` instead
`static String`	`JPA_LIST_COMPLIANCE`	Deprecated. Use `DEFAULT_LIST_SEMANTICS` instead.
`static String`	`JPA_LOAD_BY_ID_COMPLIANCE`	Determines if an identifier value passed to `EntityManager.find(java.lang.Class<T>, java.lang.Object)` or `EntityManager.getReference(java.lang.Class<T>, java.lang.Object)` may be coerced to the identifier type declared by the entity.
`static String`	`JPA_LOCK_SCOPE`	Deprecated. Use `JAKARTA_LOCK_SCOPE` instead
`static String`	`JPA_LOCK_TIMEOUT`	Deprecated. Use `JAKARTA_LOCK_TIMEOUT` instead
`static String`	`JPA_METAMODEL_POPULATION`	Setting that indicates whether to build the JPA types, either: enabled - Do the build disabled - Do not do the build ignoreUnsupported - Do the build, but ignore any non-JPA features that would otherwise result in a failure.
`static String`	`JPA_NON_JTA_DATASOURCE`	Deprecated. Use `JAKARTA_NON_JTA_DATASOURCE` instead
`static String`	`JPA_ORDER_BY_MAPPING_COMPLIANCE`	JPA specifies that items occurring in `OrderBy` lists must be references to entity attributes, whereas Hibernate, by default, allows more complex expressions.
`static String`	`JPA_PERSIST_VALIDATION_GROUP`	Deprecated. Use `JAKARTA_PERSIST_VALIDATION_GROUP` instead
`static String`	`JPA_PERSISTENCE_PROVIDER`	Deprecated. Use `JAKARTA_PERSISTENCE_PROVIDER` instead
`static String`	`JPA_PROXY_COMPLIANCE`	The JPA specification insists that an `EntityNotFoundException` must be thrown whenever an uninitialized entity proxy with no corresponding row in the database is accessed.
`static String`	`JPA_QUERY_COMPLIANCE`	When enabled, specifies that every query must strictly follow the specified behavior of `Query`.
`static String`	`JPA_REMOVE_VALIDATION_GROUP`	Deprecated. Use `JAKARTA_REMOVE_VALIDATION_GROUP` instead
`static String`	`JPA_SHARED_CACHE_MODE`	Deprecated. Use `JAKARTA_SHARED_CACHE_MODE` instead
`static String`	`JPA_SHARED_CACHE_RETRIEVE_MODE`	Deprecated. Use `JAKARTA_SHARED_CACHE_RETRIEVE_MODE` instead
`static String`	`JPA_SHARED_CACHE_STORE_MODE`	Deprecated. Use `JAKARTA_SHARED_CACHE_STORE_MODE` instead
`static String`	`JPA_TRANSACTION_COMPLIANCE`	When enabled, specifies that the Hibernate `Transaction` should behave according to the semantics defined by the JPA specification for an `EntityTransaction`.
`static String`	`JPA_TRANSACTION_TYPE`	Deprecated. Use `JAKARTA_TRANSACTION_TYPE` instead
`static String`	`JPA_UPDATE_VALIDATION_GROUP`	Deprecated. Use `JAKARTA_UPDATE_VALIDATION_GROUP` instead
`static String`	`JPA_VALIDATION_FACTORY`	Deprecated. Use `JAKARTA_VALIDATION_FACTORY` instead
`static String`	`JPA_VALIDATION_MODE`	Deprecated. Use `JAKARTA_VALIDATION_MODE` instead
`static String`	`JPAQL_STRICT_COMPLIANCE`
`static String`	`JSON_FORMAT_MAPPER`	Specifies a `FormatMapper` used for for JSON serialization and deserialization, either: an instance of `FormatMapper`, a `Class` representing a class that implements `FormatMapper`, the name of a class that implements `FormatMapper`, or one of the short hand constants `jackson` or `jsonb`.
`static String`	`JTA_CACHE_TM`	When enabled, indicates that it is safe to cache `TransactionManager` references.
`static String`	`JTA_CACHE_UT`	When enabled, indicates that it is safe to cache `UserTransaction` references.
`static String`	`JTA_PLATFORM`	Specifies the `JtaPlatform` implementation to use for integrating with JTA, either: an instance of `JtaPlatform`, or the name of a class that implements `JtaPlatform`.
`static String`	`JTA_PLATFORM_RESOLVER`	Specifies a `JtaPlatformResolver` implementation that should be used to obtain an instance of `JtaPlatform`.
`static String`	`JTA_TRACK_BY_THREAD`	A transaction can be rolled back by another thread ("tracking by thread") -- not the original application.
`static String`	`KEYWORD_AUTO_QUOTING_ENABLED`	Specifies whether to automatically quote any names that are deemed SQL keywords.
`static String`	`LOADED_CLASSES`
`static String`	`LOG_JDBC_WARNINGS`	When enabled, specifies that JDBC statement warnings should be logged.
`static String`	`LOG_SESSION_METRICS`	Controls whether session metrics should be logged for any session in which statistics are being collected.
`static String`	`LOG_SLOW_QUERY`	Specifies a duration in milliseconds defining the minimum query execution time that characterizes a "slow" query.
`static String`	`MAX_FETCH_DEPTH`	Specifies the maximum depth of nested outer join fetching.
`static String`	`MERGE_ENTITY_COPY_OBSERVER`	Setting that specifies how Hibernate will respond when multiple representations of the same persistent entity ("entity copy") are detected while merging.
`static String`	`MULTI_TENANT_CONNECTION_PROVIDER`	Specifies a `MultiTenantConnectionProvider` to use.
`static String`	`MULTI_TENANT_IDENTIFIER_RESOLVER`	Specifies a `CurrentTenantIdentifierResolver` to use, either: an instance of `CurrentTenantIdentifierResolver`, a `Class` representing an class that implements `CurrentTenantIdentifierResolver`, or the name of a class that implements `CurrentTenantIdentifierResolver`.
`static String`	`NON_CONTEXTUAL_LOB_CREATION`	When enabled, specifies that Hibernate should not use contextual LOB creation.
`static String`	`ORDER_INSERTS`	Enable ordering of insert statements for the purpose of more efficient JDBC batching.
`static String`	`ORDER_UPDATES`	Enable ordering of update statements by primary key value.
`static String`	`ORM_XML_FILES`
`static String`	`PASS`	Specifies password to use when connecting via JDBC.
`static String`	`PERSISTENCE_UNIT_NAME`	Specifies the name of the persistence unit.
`static String`	`PHYSICAL_NAMING_STRATEGY`	Specifies the `PhysicalNamingStrategy` to use.
`static String`	`POOL_SIZE`	Specifies the maximum number of inactive connections for the built-in connection pool.
`static String`	`PREFER_USER_TRANSACTION`	When enabled, specifies that the `UserTransaction` should be used in preference to the `TransactionManager` for JTA transaction management.
`static String`	`PREFERRED_BOOLEAN_JDBC_TYPE_CODE`	Specifies the preferred JDBC type code for storing boolean values.
`static String`	`PREFERRED_POOLED_OPTIMIZER`	When a generator specifies an increment-size and an optimizer was not explicitly specified, which of the "pooled" optimizers should be preferred? Can specify an optimizer short name or the name of a class which implements `Optimizer`.
`static String`	`PROXOOL_CONFIG_PREFIX`	A setting prefix used to indicate settings that target the hibernate-proxool integration
`static String`	`PROXOOL_EXISTING_POOL`	Proxool property to configure the Proxool Provider from an already existing pool (`true` / `false`)
`static String`	`PROXOOL_POOL_ALIAS`	Proxool property with the Proxool pool alias to use (Required for `PROXOOL_EXISTING_POOL`, `PROXOOL_PROPERTIES`, or `PROXOOL_XML`)
`static String`	`PROXOOL_PROPERTIES`	Proxool property to configure the Proxool provider using a properties file (`/path/to/proxool.properties`)
`static String`	`PROXOOL_XML`	Proxool property to configure the Proxool provider using an XML (`/path/to/file.xml`)
`static String`	`QUERY_CACHE_FACTORY`	Specifies the `TimestampsCacheFactory` to use.
`static String`	`QUERY_MULTI_TABLE_INSERT_STRATEGY`	Defines the "global" strategy to use for handling HQL and Criteria insert queries.
`static String`	`QUERY_MULTI_TABLE_MUTATION_STRATEGY`	Defines the "global" strategy to use for handling HQL and Criteria mutation queries.
`static String`	`QUERY_PLAN_CACHE_ENABLED`	When enabled, specifies that query plans should be cached.
`static String`	`QUERY_PLAN_CACHE_MAX_SIZE`	The maximum number of entries in the query plan cache or query interpretation cache.
`static String`	`QUERY_PLAN_CACHE_PARAMETER_METADATA_MAX_SIZE`	Deprecated. this setting is not currently used
`static String`	`QUERY_STARTUP_CHECKING`	When enabled, specifies that named queries be checked during startup.
`static String`	`QUERY_STATISTICS_MAX_SIZE`	This setting controls the number of `QueryStatistics` entries that will be stored by the Hibernate `Statistics` object.
`static String`	`SCANNER`	Specifies an implementation of `Scanner`, either: an instance of `Scanner`, a `Class` representing a class that implements `Scanner` the name of a class that implements `Scanner`.
`static String`	`SCANNER_ARCHIVE_INTERPRETER`	Specifies an `ArchiveDescriptorFactory` to use in the scanning process, either: an instance of `ArchiveDescriptorFactory`, a `Class` representing a class that implements `ArchiveDescriptorFactory`, or the name of a class that implements `ArchiveDescriptorFactory`.
`static String`	`SCANNER_DISCOVERY`	Identifies a comma-separated list of values indicating the types of things we should auto-detect during scanning.
`static String`	`SCHEMA_MANAGEMENT_TOOL`	Specifies the `SchemaManagementTool` to use for performing schema management.
`static String`	`SEMANTIC_QUERY_PRODUCER`	Specifies a `HqlTranslator` to use for HQL query translation.
`static String`	`SEMANTIC_QUERY_TRANSLATOR`	Specifies a `SqmTranslatorFactory` to use for HQL query translation.
`static String`	`SEQUENCE_INCREMENT_SIZE_MISMATCH_STRATEGY`	This setting defines the `SequenceMismatchStrategy` used when Hibernate detects a mismatch between a sequence configuration in an entity mapping and its database sequence object counterpart.
`static String`	`SESSION_FACTORY_NAME`	Setting used to name the Hibernate `SessionFactory`.
`static String`	`SESSION_FACTORY_NAME_IS_JNDI`	Does the value defined by `SESSION_FACTORY_NAME` represent a JNDI namespace into which the `SessionFactory` should be bound and made accessible?
`static String`	`SESSION_FACTORY_OBSERVER`	Specifies a class which implements `SessionFactoryObserver` and has a constructor with no parameters.
`static String`	`SESSION_SCOPED_INTERCEPTOR`	Specifies an `Interceptor` implementation associated with the `SessionFactory` and propagated to each `Session` created from the `SessionFactory`.
`static String`	`SHOW_SQL`	Enables logging of generated SQL to the console.
`static String`	`STATEMENT_BATCH_SIZE`	Specifies the maximum JDBC batch size.
`static String`	`STATEMENT_FETCH_SIZE`	Gives the JDBC driver a hint as to the number of rows that should be fetched from the database when more rows are needed.
`static String`	`STATEMENT_INSPECTOR`	Specifies a `StatementInspector` implementation associated with the `SessionFactory`, either: an instance of `StatementInspector`, a `Class` representing an class that implements `StatementInspector`, or the name of a class that implements `StatementInspector`.
`static String`	`STATIC_METAMODEL_POPULATION`	Setting that controls whether we seek out JPA "static metamodel" classes and populate them, either: enabled -Do the population disabled - Do not do the population skipUnsupported - Do the population, but ignore any non-JPA features that would otherwise result in the population failing.
`static String`	`STORAGE_ENGINE`	Specifies the default storage engine for a relational databases that supports multiple storage engines.
`static String`	`TABLE_GENERATOR_STORE_LAST_USED`	Determines if the identifier value stored in the database table backing a table generator is the last value returned by the identifier generator, or the next value to be returned.
`static String`	`TC_CLASSLOADER`	Specifies how the thread context class loader must be used for class lookup.
`static String`	`TIMEZONE_DEFAULT_STORAGE`	Specifies the default strategy for storage of the timezone information for zoned datetime types: `TimeZoneStorageType.NORMALIZE`, `TimeZoneStorageType.COLUMN`, `TimeZoneStorageType.NATIVE`, or `TimeZoneStorageType.AUTO`.
`static String`	`TRANSACTION_COORDINATOR_STRATEGY`	Specify the `TransactionCoordinatorBuilder` implementation to use for creating instances of `TransactionCoordinator`, either: an instance of `TransactionCoordinatorBuilder`, a `Class` representing a class that implements `TransactionCoordinatorBuilder`, or the name of a class that implements `TransactionCoordinatorBuilder`.
`static String`	`UNIQUE_CONSTRAINT_SCHEMA_UPDATE_STRATEGY`	Unique columns and unique keys both use unique constraints in most dialects.
`static String`	`URL`	Specifies the JDBC connection URL.
`static String`	`USE_DIRECT_REFERENCE_CACHE_ENTRIES`	Enable direct storage of entity references into the second level cache when applicable.
`static String`	`USE_ENTITY_WHERE_CLAUSE_FOR_COLLECTIONS`	The `Where` annotation specifies a restriction on the table rows which are visible as entity class instances or collection elements.
`static String`	`USE_GET_GENERATED_KEYS`	Specifies that generated primary keys may be retrieved using the JDBC 3 `Statement.getGeneratedKeys()` operation.
`static String`	`USE_IDENTIFIER_ROLLBACK`
`static String`	`USE_MINIMAL_PUTS`	Optimize interaction with the second-level cache to minimize writes, at the cost of more frequent database reads.
`static String`	`USE_NATIONALIZED_CHARACTER_DATA`	By default, Hibernate maps character data represented by `String`s and `Clob`s to the JDBC types `Types.VARCHAR` and `Types.CLOB`.
`static String`	`USE_QUERY_CACHE`	Enable the query cache (disabled by default).
`static String`	`USE_REFLECTION_OPTIMIZER`	When enabled, specifies that property access should be optimized via the use of generated bytecode.
`static String`	`USE_SCROLLABLE_RESULTSET`	When enabled, specifies that JDBC scrollable `ResultSet`s may be used.
`static String`	`USE_SECOND_LEVEL_CACHE`	When enabled, specifies that the second-level cache may be used.
`static String`	`USE_SQL_COMMENTS`	Specifies that comments should be added to the generated SQL.
`static String`	`USE_STRUCTURED_CACHE`	Enables the use of structured second-level cache entries.
`static String`	`USER`	Specifies the database user to use when connecting via JDBC.
`static String`	`XML_MAPPING_ENABLED`	When disabled, specifies that processing of XML-based mappings should be skipped.

- Field Detail
  - JAKARTA_PERSISTENCE_PROVIDER
```
static final String JAKARTA_PERSISTENCE_PROVIDER
```
    Specifies a class implementing PersistenceProvider.
    See JPA 2 sections 9.4.3 and 8.2.1.4
    
    See Also:
    
    Constant Field Values
  - JAKARTA_TRANSACTION_TYPE
```
static final String JAKARTA_TRANSACTION_TYPE
```
    Specifies the type of transactions supported by the entity managers.
    See JPA 2 sections 9.4.3 and 8.2.1.2
    
    See Also:
    
    Constant Field Values
  - JAKARTA_JTA_DATASOURCE
```
static final String JAKARTA_JTA_DATASOURCE
```
    Specifies the JNDI name of a JTA DataSource.
    See JPA 2 sections 9.4.3 and 8.2.1.5
    
    See Also:
    
    Constant Field Values
  - JAKARTA_NON_JTA_DATASOURCE
```
static final String JAKARTA_NON_JTA_DATASOURCE
```
    Specifies the JNDI name of a non-JTA DataSource.
    See JPA 2 sections 9.4.3 and 8.2.1.5
    
    See Also:
    
    Constant Field Values
  - JAKARTA_JDBC_DRIVER
```
static final String JAKARTA_JDBC_DRIVER
```
    Specifies the name of a JDBC driver to use to connect to the database.
    Used in conjunction with JPA_JDBC_URL, JPA_JDBC_USER and JPA_JDBC_PASSWORD to specify how to connect to the database.
    When connections are obtained from a DataSource, use either JPA_JTA_DATASOURCE or JPA_NON_JTA_DATASOURCE instead.
    See section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JAKARTA_JDBC_URL
```
static final String JAKARTA_JDBC_URL
```
    Specifies the JDBC connection URL to use to connect to the database.
    Used in conjunction with JPA_JDBC_DRIVER, JPA_JDBC_USER and JPA_JDBC_PASSWORD to specify how to connect to the database.
    When connections are obtained from a DataSource, use either JPA_JTA_DATASOURCE or JPA_NON_JTA_DATASOURCE instead.
    See section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JAKARTA_JDBC_USER
```
static final String JAKARTA_JDBC_USER
```
    Specifies the database user to use when connecting via JDBC.
    Used in conjunction with JPA_JDBC_DRIVER, JPA_JDBC_URL and JPA_JDBC_PASSWORD to specify how to connect to the database.
    See section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JAKARTA_JDBC_PASSWORD
```
static final String JAKARTA_JDBC_PASSWORD
```
    Specifies the password to use when connecting via JDBC.
    Used in conjunction with JPA_JDBC_DRIVER, JPA_JDBC_URL and JPA_JDBC_USER to specify how to connect to the database.
    See JPA 2 section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JAKARTA_SHARED_CACHE_MODE
```
static final String JAKARTA_SHARED_CACHE_MODE
```
    When enabled, specifies that the second-level cache (which JPA calls the "shared" cache) may be used, as per the rules defined in JPA 2 section 3.1.7.
    See JPA 2 sections 9.4.3 and 8.2.1.7
    
    See Also:
    
    SharedCacheMode, Constant Field Values
  - JAKARTA_SHARED_CACHE_RETRIEVE_MODE
```
static final String JAKARTA_SHARED_CACHE_RETRIEVE_MODE
```
    See Also:
    
    SpecHints.HINT_SPEC_CACHE_RETRIEVE_MODE, Constant Field Values
  - JAKARTA_SHARED_CACHE_STORE_MODE
```
static final String JAKARTA_SHARED_CACHE_STORE_MODE
```
    See Also:
    
    SpecHints.HINT_SPEC_CACHE_STORE_MODE, Constant Field Values
  - JAKARTA_VALIDATION_MODE
```
static final String JAKARTA_VALIDATION_MODE
```
    Indicates which form of automatic validation is in effect as per the rules defined in JPA 2 section 3.6.1.1.
    See JPA 2 sections 9.4.3 and 8.2.1.8
    
    See Also:
    
    ValidationMode, Constant Field Values
  - JAKARTA_VALIDATION_FACTORY
```
static final String JAKARTA_VALIDATION_FACTORY
```
    Used to pass along any discovered ValidatorFactory.
    
    See Also:
    
    Constant Field Values
  - JAKARTA_PERSIST_VALIDATION_GROUP
```
static final String JAKARTA_PERSIST_VALIDATION_GROUP
```
    Used to coordinate with bean validators.
    See JPA 2 section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JAKARTA_UPDATE_VALIDATION_GROUP
```
static final String JAKARTA_UPDATE_VALIDATION_GROUP
```
    Used to coordinate with bean validators.
    See JPA 2 section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JAKARTA_REMOVE_VALIDATION_GROUP
```
static final String JAKARTA_REMOVE_VALIDATION_GROUP
```
    Used to coordinate with bean validators.
    See JPA 2 section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JAKARTA_LOCK_SCOPE
```
static final String JAKARTA_LOCK_SCOPE
```
    Used to request (hint) a pessimistic lock scope.
    See JPA 2 sections 8.2.1.9 and 3.4.4.3
    
    See Also:
    
    Constant Field Values
  - JAKARTA_LOCK_TIMEOUT
```
static final String JAKARTA_LOCK_TIMEOUT
```
    Used to request (hint) a pessimistic lock timeout in milliseconds.
    See JPA 2 sections 8.2.1.9 and 3.4.4.3
    
    See Also:
    
    Constant Field Values
  - JAKARTA_CDI_BEAN_MANAGER
```
static final String JAKARTA_CDI_BEAN_MANAGER
```
    Used to pass a CDI BeanManager to Hibernate.
    According to the JPA specification, the BeanManager should be passed at boot time and be ready for immediate use at that time. But not all environments can do this (WildFly, for example). To accommodate such environments, Hibernate provides two options:
    
    A proprietary CDI extension SPI (which has been proposed to the CDI spec group as a standard option) which can be used to provide delayed BeanManager access: to use this solution, the reference passed as the BeanManager during bootstrap should be typed as ExtendedBeanManager.
    Delayed access to the BeanManager reference: here, Hibernate will not access the reference passed as the BeanManager during bootstrap until it is first needed. Note, however, that this has the effect of delaying the detection of any deployment problems until after bootstrapping.
    This setting is used to configure access to the BeanManager, either directly, or via ExtendedBeanManager.
    See Also:
    
    Constant Field Values
  - CLASSLOADERS
```
static final String CLASSLOADERS
```
    Specifies a collection of the ClassLoader instances Hibernate should use for classloading and resource loading.
    
    Since:
    
    5.0
    
    See Also:
    
    Constant Field Values
  - TC_CLASSLOADER
```
static final String TC_CLASSLOADER
```
    Specifies how the thread context class loader must be used for class lookup.
    
    See Also:
    
    TcclLookupPrecedence, Constant Field Values
  - JPA_METAMODEL_POPULATION
```
static final String JPA_METAMODEL_POPULATION
```
    Setting that indicates whether to build the JPA types, either:
    
    enabled - Do the build
    
    disabled - Do not do the build
    
    ignoreUnsupported - Do the build, but ignore any non-JPA features that would otherwise result in a failure.
    See Also:
    
    Constant Field Values
  - STATIC_METAMODEL_POPULATION
```
static final String STATIC_METAMODEL_POPULATION
```
    Setting that controls whether we seek out JPA "static metamodel" classes and populate them, either:
    
    enabled -Do the population
    
    disabled - Do not do the population
    
    skipUnsupported - Do the population, but ignore any non-JPA features that would otherwise result in the population failing.
    See Also:
    
    Constant Field Values
  - CONNECTION_PROVIDER
```
static final String CONNECTION_PROVIDER
```
    Specifies a ConnectionProvider to use for obtaining JDBC connections, either:
    
    an instance of ConnectionProvider,
    a Class representing a class that implements ConnectionProvider, or
    the name of a class that implements ConnectionProvider.
    
    The term "class" appears in the setting name due to legacy reasons; however it can accept instances.
    See Also:
    
    Constant Field Values
  - DRIVER
```
static final String DRIVER
```
    Specifies the JDBC driver class.
    
    See Also:
    
    Constant Field Values
  - URL
```
static final String URL
```
    Specifies the JDBC connection URL.
    
    See Also:
    
    Constant Field Values
  - USER
```
static final String USER
```
    Specifies the database user to use when connecting via JDBC.
    Depending on the configured ConnectionProvider, the specified username might be used to:
    
    create a JDBC connection using DriverManager.getConnection(String,java.util.Properties) or Driver.connect(String,java.util.Properties), or
    obtain a JDBC connection from a datasource, using DataSource.getConnection(String, String).
    See Also:
    
    PASS, Constant Field Values
  - PASS
```
static final String PASS
```
    Specifies password to use when connecting via JDBC.
    
    See Also:
    
    USER, Constant Field Values
  - ISOLATION
```
static final String ISOLATION
```
    Specified the JDBC transaction isolation level.
    
    See Also:
    
    Constant Field Values
  - AUTOCOMMIT
```
static final String AUTOCOMMIT
```
    Controls the autocommit mode of JDBC connections obtained from any ConnectionProvider implementation which respects this setting, which the built-in implementations do, except for DatasourceConnectionProviderImpl.
    
    See Also:
    
    Constant Field Values
  - POOL_SIZE
```
static final String POOL_SIZE
```
    Specifies the maximum number of inactive connections for the built-in connection pool.
    
    See Also:
    
    Constant Field Values
  - DATASOURCE
```
static final String DATASOURCE
```
    Specifies a DataSource, either:
    
    an instance of DataSource, or
    a JNDI name under which to obtain the DataSource.
    For JNDI names, see also JNDI_CLASS, JNDI_URL, JNDI_PREFIX, etc.
    See Also:
    
    Constant Field Values
  - CONNECTION_PROVIDER_DISABLES_AUTOCOMMIT
```
static final String CONNECTION_PROVIDER_DISABLES_AUTOCOMMIT
```
    Allows a user to tell Hibernate that the connections we obtain from the configured ConnectionProvider will already have autocommit disabled when we acquire them from the provider. When we obtain connections with autocommit already disabled, we may circumvent some operations in the interest of performance.
    By default, Hibernate calls Connection.setAutoCommit(boolean) on newly-obtained connections.
    
    Since:
    
    5.2.10
    
    See Also:
    
    Constant Field Values
  - CONNECTION_PREFIX
```
static final String CONNECTION_PREFIX
```
    A prefix for properties specifying arbitrary JDBC connection properties. These properties are simply passed along to the provider when creating a connection.
    
    See Also:
    
    Constant Field Values
  - JNDI_CLASS
```
static final String JNDI_CLASS
```
    Specifies the JNDI InitialContext implementation class.
    
    See Also:
    
    Context.INITIAL_CONTEXT_FACTORY, Constant Field Values
  - JNDI_URL
```
static final String JNDI_URL
```
    Specifies the JNDI provider/connection URL.
    
    See Also:
    
    Context.PROVIDER_URL, Constant Field Values
  - JNDI_PREFIX
```
static final String JNDI_PREFIX
```
    A prefix for properties specifying arbitrary JNDI InitialContext properties. These properties are simply passed along to the constructor InitialContext(java.util.Hashtable).
    
    See Also:
    
    Constant Field Values
  - DIALECT
```
static final String DIALECT
```
    Specifies the Hibernate SQL Dialect class.
    
    See Also:
    
    Dialect, Constant Field Values
  - DIALECT_RESOLVERS
```
static final String DIALECT_RESOLVERS
```
    Specifies additional DialectResolver implementations to register with the standard DialectFactory.
    
    See Also:
    
    Constant Field Values
  - DIALECT_DB_NAME
```
@Deprecated
static final String DIALECT_DB_NAME
```
    Deprecated.
    Use JAKARTA_HBM2DDL_DB_NAME instead
    
    Specifies the name of the database provider in cases where a connection to the database is not available (usually for generating scripts). In such cases, a value for this setting must be specified.
    The value of this setting is expected to match the value returned by DatabaseMetaData.getDatabaseProductName() for the target database.
    Additionally, specifying "javax.persistence.database-major-version", and perhaps even "javax.persistence.database-minor-version", may be required for high quality DDL generation.
    
    See Also:
    
    DIALECT_DB_VERSION, DIALECT_DB_MAJOR_VERSION, DIALECT_DB_MINOR_VERSION, Constant Field Values
  - DIALECT_DB_VERSION
```
@Deprecated
static final String DIALECT_DB_VERSION
```
    Deprecated.
    Use JAKARTA_HBM2DDL_DB_VERSION instead
    
    Specifies the name of the database provider in cases where a connection to the database is not available (usually for generating scripts). This value is used to help more precisely determine how to perform schema generation tasks for the underlying database in cases where "javax.persistence.database-product-name" does not provide enough distinction.
    The value of this setting is expected to match the value returned by DatabaseMetaData.getDatabaseProductVersion() for the target database.
    
    See Also:
    
    DIALECT_DB_NAME, Constant Field Values
  - DIALECT_DB_MAJOR_VERSION
```
@Deprecated
static final String DIALECT_DB_MAJOR_VERSION
```
    Deprecated.
    Use JAKARTA_HBM2DDL_DB_MAJOR_VERSION instead
    
    Specifies the major version of the underlying database, as would be returned by DatabaseMetaData.getDatabaseMajorVersion() for the target database. This value is used to help more precisely determine how to perform schema generation tasks for the database in cases where "javax.persistence.database-product-name" does not provide enough distinction.
    
    See Also:
    
    DIALECT_DB_NAME, DIALECT_DB_MINOR_VERSION, Constant Field Values
  - DIALECT_DB_MINOR_VERSION
```
@Deprecated
static final String DIALECT_DB_MINOR_VERSION
```
    Deprecated.
    Use JAKARTA_HBM2DDL_DB_MINOR_VERSION instead
    
    Specifies the minor version of the underlying database, as would be returned by DatabaseMetaData.getDatabaseMinorVersion() for the target database. This setting is used in Dialect resolution.
    
    See Also:
    
    DIALECT_DB_NAME, DIALECT_DB_MAJOR_VERSION, DialectResolver, Constant Field Values
  - STORAGE_ENGINE
```
static final String STORAGE_ENGINE
```
    Specifies the default storage engine for a relational databases that supports multiple storage engines. This property must be set either as an Environment variable or JVM System Property, since the Dialect is instantiated before Hibernate property resolution.
    
    Since:
    
    5.2.9
    
    See Also:
    
    Constant Field Values
  - SCHEMA_MANAGEMENT_TOOL
```
static final String SCHEMA_MANAGEMENT_TOOL
```
    Specifies the SchemaManagementTool to use for performing schema management.
    By default, HibernateSchemaManagementTool is used.
    
    Since:
    
    5.0
    
    See Also:
    
    Constant Field Values
  - TRANSACTION_COORDINATOR_STRATEGY
```
static final String TRANSACTION_COORDINATOR_STRATEGY
```
    Specify the TransactionCoordinatorBuilder implementation to use for creating instances of TransactionCoordinator, either:
    
    an instance of TransactionCoordinatorBuilder,
    a Class representing a class that implements TransactionCoordinatorBuilder, or
    the name of a class that implements TransactionCoordinatorBuilder.
    Since:
    
    5.0
    
    See Also:
    
    Constant Field Values
  - JTA_PLATFORM
```
static final String JTA_PLATFORM
```
    Specifies the JtaPlatform implementation to use for integrating with JTA, either:
    
    an instance of JtaPlatform, or
    the name of a class that implements JtaPlatform.
    Since:
    
    4.0
    
    See Also:
    
    JTA_PLATFORM_RESOLVER, Constant Field Values
  - PREFER_USER_TRANSACTION
```
static final String PREFER_USER_TRANSACTION
```
    When enabled, specifies that the UserTransaction should be used in preference to the TransactionManager for JTA transaction management.
    By default, the TransactionManager is preferred.
    
    Since:
    
    5.0
    
    See Also:
    
    JtaPlatform.retrieveUserTransaction(), JtaPlatform.retrieveTransactionManager(), Constant Field Values
  - JTA_PLATFORM_RESOLVER
```
static final String JTA_PLATFORM_RESOLVER
```
    Specifies a JtaPlatformResolver implementation that should be used to obtain an instance of JtaPlatform.
    
    Since:
    
    4.3
    
    See Also:
    
    JTA_PLATFORM, Constant Field Values
  - JTA_CACHE_TM
```
static final String JTA_CACHE_TM
```
    When enabled, indicates that it is safe to cache TransactionManager references.
    
    Since:
    
    4.0
    
    See Also:
    
    Constant Field Values
  - JTA_CACHE_UT
```
static final String JTA_CACHE_UT
```
    When enabled, indicates that it is safe to cache UserTransaction references.
    
    Since:
    
    4.0
    
    See Also:
    
    Constant Field Values
  - DEFAULT_CATALOG
```
static final String DEFAULT_CATALOG
```
    A default database catalog name to use for unqualified table names
    
    See Also:
    
    MetadataBuilder.applyImplicitCatalogName(java.lang.String), Constant Field Values
  - DEFAULT_SCHEMA
```
static final String DEFAULT_SCHEMA
```
    A default database schema (owner) name to use for unqualified table names
    
    See Also:
    
    MetadataBuilder.applyImplicitSchemaName(java.lang.String), Constant Field Values
  - DEFAULT_CACHE_CONCURRENCY_STRATEGY
```
static final String DEFAULT_CACHE_CONCURRENCY_STRATEGY
```
    Specifies the CacheConcurrencyStrategy to use by default when an entity is marked @Cacheable, but no concurrency strategy is explicitly specified via the Cache annotation.
    An explicit strategy may be specified using @Cache(usage=...).
    
    See Also:
    
    MetadataBuilder.applyAccessType(org.hibernate.cache.spi.access.AccessType), Constant Field Values
  - FORCE_DISCRIMINATOR_IN_SELECTS_BY_DEFAULT
```
static final String FORCE_DISCRIMINATOR_IN_SELECTS_BY_DEFAULT
```
    See Also:
    
    MetadataBuilder.enableImplicitForcingOfDiscriminatorsInSelect(boolean), Constant Field Values
  - IMPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS
```
static final String IMPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS
```
    The legacy behavior of Hibernate is to not use discriminators for joined inheritance (Hibernate does not need the discriminator.). However, some JPA providers do need the discriminator for handling joined inheritance, so in the interest of portability this capability has been added to Hibernate.
    However, we want to make sure that legacy applications continue to work as well. Which puts us in a bind in terms of how to handle "implicit" discriminator mappings. The solution is to assume that the absence of discriminator metadata means to follow the legacy behavior unless this setting is enabled. With this setting enabled, Hibernate will interpret the absence of discriminator metadata as an indication to use the JPA defined defaults for these absent annotations.
    See Hibernate Jira issue HHH-6911 for additional background info.
    
    See Also:
    
    MetadataBuilder.enableImplicitDiscriminatorsForJoinedSubclassSupport(boolean), IGNORE_EXPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS, Constant Field Values
  - IGNORE_EXPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS
```
static final String IGNORE_EXPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS
```
    The legacy behavior of Hibernate is to not use discriminators for joined inheritance (Hibernate does not need the discriminator). However, some JPA providers do need the discriminator for handling joined inheritance, so in the interest of portability this capability has been added to Hibernate.
    Existing applications rely (implicitly or explicitly) on Hibernate ignoring any DiscriminatorColumn declarations on joined inheritance hierarchies. This setting allows these applications to maintain the legacy behavior of @DiscriminatorColumn annotations being ignored when paired with joined inheritance.
    See Hibernate Jira issue HHH-6911 for additional background info.
    
    See Also:
    
    MetadataBuilder.enableExplicitDiscriminatorsForJoinedSubclassSupport(boolean), IMPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS, Constant Field Values
  - USE_NATIONALIZED_CHARACTER_DATA
```
static final String USE_NATIONALIZED_CHARACTER_DATA
```
    By default, Hibernate maps character data represented by Strings and Clobs to the JDBC types Types.VARCHAR and Types.CLOB. This setting, when enabled, turns on the use of explicit nationalized character support for mappings involving character data, specifying that the JDBC types Types.NVARCHAR and Types.NCLOB should be used instead.
    This setting is relevant for use with databases with explicit nationalization support, and it is not needed for databases whose native varchar and clob types support Unicode data. (If you're not sure how your database handles Unicode, check out the implementation of Dialect.getNationalizationSupport() for its SQL dialect.)
    Enabling this setting has two effects:
    
    when interacting with JDBC, Hibernate uses operations like PreparedStatement.setNString(int, String) PreparedStatement.setNClob(int, java.sql.NClob) to pass character data, and
    when generating DDL, the schema export tool uses nchar, nvarchar, or nclob as the generated column type when no column type is explicitly specified using Column.columnDefinition().
    This setting is disabled by default, and so Unicode character data may not be persisted correctly for databases with explicit nationalization support.
    This is a global setting applying to all mappings associated with a given SessionFactory. The Nationalized annotation may be used to selectively enable nationalized character support for specific columns.
    See Also:
    
    MetadataBuilder.enableGlobalNationalizedCharacterDataSupport(boolean), NationalizationSupport, Nationalized, Constant Field Values
  - SCANNER
```
static final String SCANNER
```
    Specifies an implementation of Scanner, either:
    
    an instance of Scanner,
    a Class representing a class that implements Scanner
    the name of a class that implements Scanner.
    See Also:
    
    MetadataBuilder.applyScanner(org.hibernate.boot.archive.scan.spi.Scanner), Constant Field Values
  - SCANNER_ARCHIVE_INTERPRETER
```
static final String SCANNER_ARCHIVE_INTERPRETER
```
    Specifies an ArchiveDescriptorFactory to use in the scanning process, either:
    
    an instance of ArchiveDescriptorFactory,
    a Class representing a class that implements ArchiveDescriptorFactory, or
    the name of a class that implements ArchiveDescriptorFactory.
    
    See information on Scanner about expected constructor forms.
    See Also:
    
    SCANNER, Scanner, AbstractScannerImpl, MetadataBuilder.applyArchiveDescriptorFactory(org.hibernate.boot.archive.spi.ArchiveDescriptorFactory), Constant Field Values
  - SCANNER_DISCOVERY
```
static final String SCANNER_DISCOVERY
```
    Identifies a comma-separated list of values indicating the types of things we should auto-detect during scanning. Allowable values include:
    
    "class" specifies that .class files are discovered as managed classes
    "hbm" specifies that hbm.xml files are discovered as mapping files
    See Also:
    
    MetadataBuilder.applyScanOptions(org.hibernate.boot.archive.scan.spi.ScanOptions), Constant Field Values
  - IMPLICIT_NAMING_STRATEGY
```
static final String IMPLICIT_NAMING_STRATEGY
```
    Used to specify the ImplicitNamingStrategy class to use. The following shortcut names are defined for this setting:
    
    "default" is an abbreviation for ImplicitNamingStrategyJpaCompliantImpl
    "jpa" is an abbreviation for ImplicitNamingStrategyJpaCompliantImpl
    "legacy-jpa" is an abbreviation for ImplicitNamingStrategyLegacyJpaImpl
    "legacy-hbm" is an abbreviation for ImplicitNamingStrategyLegacyHbmImpl
    "component-path" is an abbreviation for ImplicitNamingStrategyComponentPathImpl
    The default is defined by the ImplicitNamingStrategy registered under the "default" key. If that happens to be empty, the fallback is to use ImplicitNamingStrategyJpaCompliantImpl.
    Since:
    
    5.0
    
    See Also:
    
    MetadataBuilder.applyImplicitNamingStrategy(org.hibernate.boot.model.naming.ImplicitNamingStrategy), Constant Field Values
  - PHYSICAL_NAMING_STRATEGY
```
static final String PHYSICAL_NAMING_STRATEGY
```
    Specifies the PhysicalNamingStrategy to use.
    
    Since:
    
    5.0
    
    See Also:
    
    MetadataBuilder.applyPhysicalNamingStrategy(org.hibernate.boot.model.naming.PhysicalNamingStrategy), Constant Field Values
  - ARTIFACT_PROCESSING_ORDER
```
static final String ARTIFACT_PROCESSING_ORDER
```
    Specifies the order in which metadata sources should be processed, is a delimited list of values defined by MetadataSourceType.
    The default is "hbm,class" which that hbm.xml files should be processed first, followed by annotations (combined with orm.xml mappings).
    
    See Also:
    
    MetadataBuilder.applySourceProcessOrdering(MetadataSourceType...), Constant Field Values
  - KEYWORD_AUTO_QUOTING_ENABLED
```
static final String KEYWORD_AUTO_QUOTING_ENABLED
```
    Specifies whether to automatically quote any names that are deemed SQL keywords.
    Auto-quoting of SQL keywords is disabled by default.
    
    Since:
    
    5.0
    
    See Also:
    
    Constant Field Values
  - XML_MAPPING_ENABLED
```
static final String XML_MAPPING_ENABLED
```
    When disabled, specifies that processing of XML-based mappings should be skipped.
    This is a performance optimization appropriate when all O/R mappings are defined exclusively using annotations.
    By default, the XML-based mappings are taken into account.
    
    Since:
    
    5.4.1
    
    See Also:
    
    Constant Field Values
  - DEFAULT_LIST_SEMANTICS
```
static final String DEFAULT_LIST_SEMANTICS
```
    Specifies the CollectionClassification to use when Hibernate detects a plural attribute typed as List with no explicit list index configuration.
    Historically Hibernate interpreted this using BAG semantics. Starting in 6.0, Hibernate now interprets this situation using LIST semantics.
    Accepts any of:
    
    an instance of CollectionClassification
    the (case insensitive) name of a CollectionClassification (bag e.g.)
    a Class representing either List or Collection
    
    Backwards compatibility can be achieved by specifying `hibernate.mapping.default_list_semantics=bag` e.g.
    Since:
    
    6.0
    
    See Also:
    
    Constant Field Values
  - SESSION_FACTORY_NAME
```
static final String SESSION_FACTORY_NAME
```
    Setting used to name the Hibernate SessionFactory.
    Naming the SessionFactory allows for it to be properly serialized across JVMs as long as the same name is used on each JVM.
    If SESSION_FACTORY_NAME_IS_JNDI is set to true, this is also the name under which the SessionFactory is bound into JNDI on startup and from which it can be obtained from JNDI.
    
    See Also:
    
    SESSION_FACTORY_NAME_IS_JNDI, SessionFactoryRegistry, Constant Field Values
  - SESSION_FACTORY_NAME_IS_JNDI
```
static final String SESSION_FACTORY_NAME_IS_JNDI
```
    Does the value defined by SESSION_FACTORY_NAME represent a JNDI namespace into which the SessionFactory should be bound and made accessible?
    Defaults to true for backwards compatibility.
    Set this to false if naming a SessionFactory is needed for serialization purposes, but no writable JNDI context exists in the runtime environment or if the user simply does not want JNDI to be used.
    
    See Also:
    
    SESSION_FACTORY_NAME, Constant Field Values
  - SHOW_SQL
```
static final String SHOW_SQL
```
    Enables logging of generated SQL to the console.
    
    See Also:
    
    Constant Field Values
  - FORMAT_SQL
```
static final String FORMAT_SQL
```
    Enables formatting of SQL logged to the console.
    
    See Also:
    
    Constant Field Values
  - HIGHLIGHT_SQL
```
static final String HIGHLIGHT_SQL
```
    Enables highlighting of SQL logged to the console using ANSI escape codes.
    
    See Also:
    
    Constant Field Values
  - USE_SQL_COMMENTS
```
static final String USE_SQL_COMMENTS
```
    Specifies that comments should be added to the generated SQL.
    
    See Also:
    
    Constant Field Values
  - MAX_FETCH_DEPTH
```
static final String MAX_FETCH_DEPTH
```
    Specifies the maximum depth of nested outer join fetching.
    
    See Also:
    
    Constant Field Values
  - DEFAULT_BATCH_FETCH_SIZE
```
static final String DEFAULT_BATCH_FETCH_SIZE
```
    Specifies the default batch size for batch fetching.
    
    See Also:
    
    BatchSize, Constant Field Values
  - USE_SCROLLABLE_RESULTSET
```
static final String USE_SCROLLABLE_RESULTSET
```
    When enabled, specifies that JDBC scrollable ResultSets may be used. This property is only necessary when there is no ConnectionProvider, that is, when the client is supplying JDBC connections.
    
    See Also:
    
    Constant Field Values
  - USE_GET_GENERATED_KEYS
```
static final String USE_GET_GENERATED_KEYS
```
    Specifies that generated primary keys may be retrieved using the JDBC 3 Statement.getGeneratedKeys() operation.
    Usually, performance will be improved if this behavior is enabled, assuming the JDBC driver supports getGeneratedKeys().
    
    See Also:
    
    Statement.getGeneratedKeys(), Constant Field Values
  - STATEMENT_FETCH_SIZE
```
static final String STATEMENT_FETCH_SIZE
```
    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, the JDBC driver's default settings will be used.
    
    See Also:
    
    ResultSet.setFetchSize(int), Constant Field Values
  - STATEMENT_BATCH_SIZE
```
static final String STATEMENT_BATCH_SIZE
```
    Specifies the maximum JDBC batch size. A nonzero value enables batch updates.
    
    See Also:
    
    Statement.executeBatch(), Constant Field Values
  - BATCH_STRATEGY
```
static final String BATCH_STRATEGY
```
    Specifies a custom BatchBuilder.
    
    See Also:
    
    Constant Field Values
  - BATCH_VERSIONED_DATA
```
static final String BATCH_VERSIONED_DATA
```
    When enabled, specifies that versioned data should be included in batching.
    
    See Also:
    
    Constant Field Values
  - JDBC_TIME_ZONE
```
static final String JDBC_TIME_ZONE
```
    Specify a time zone that should be passed to PreparedStatement.setTimestamp(int, java.sql.Timestamp, java.util.Calendar) and PreparedStatement.setTime(int, java.sql.Time, java.util.Calendar) when binding parameters.
    By default, the JVM default time zone is assumed by the JDBC driver.
    
    Since:
    
    5.2.3
    
    See Also:
    
    Constant Field Values
  - AUTO_CLOSE_SESSION
```
static final String AUTO_CLOSE_SESSION
```
    When enabled, specifies that the Session should be closed automatically at the end of each transaction.
    
    See Also:
    
    Constant Field Values
  - FLUSH_BEFORE_COMPLETION
```
static final String FLUSH_BEFORE_COMPLETION
```
    When enabled, specifies that automatic flushing should occur during the JTA Synchronization.beforeCompletion() callback.
    
    See Also:
    
    Constant Field Values
  - CONNECTION_HANDLING
```
static final String CONNECTION_HANDLING
```
    Specifies how Hibernate should manage JDBC connections in terms of acquisition and release.
    
    Since:
    
    5.2
    
    See Also:
    
    PhysicalConnectionHandlingMode, Constant Field Values
  - CURRENT_SESSION_CONTEXT_CLASS
```
static final String CURRENT_SESSION_CONTEXT_CLASS
```
    Specifies a CurrentSessionContext for scoping the current session.
    
    See Also:
    
    Constant Field Values
  - USE_IDENTIFIER_ROLLBACK
```
static final String USE_IDENTIFIER_ROLLBACK
```
    See Also:
    
    Constant Field Values
  - USE_REFLECTION_OPTIMIZER
```
static final String USE_REFLECTION_OPTIMIZER
```
    When enabled, specifies that property access should be optimized via the use of generated bytecode.
    
    See Also:
    
    Constant Field Values
  - CALLABLE_NAMED_PARAMS_ENABLED
```
static final String CALLABLE_NAMED_PARAMS_ENABLED
```
    When enabled, specifies that Hibernate should attempt to map parameter names given in a ProcedureCall or StoredProcedureQuery to named parameters of the JDBC CallableStatement.
    
    Since:
    
    6.0
    
    See Also:
    
    SessionFactoryOptions.isUseOfJdbcNamedParametersEnabled(), Constant Field Values
  - SEMANTIC_QUERY_PRODUCER
```
static final String SEMANTIC_QUERY_PRODUCER
```
    Specifies a HqlTranslator to use for HQL query translation.
    
    See Also:
    
    Constant Field Values
  - SEMANTIC_QUERY_TRANSLATOR
```
static final String SEMANTIC_QUERY_TRANSLATOR
```
    Specifies a SqmTranslatorFactory to use for HQL query translation.
    
    See Also:
    
    Constant Field Values
  - QUERY_MULTI_TABLE_MUTATION_STRATEGY
```
static final String QUERY_MULTI_TABLE_MUTATION_STRATEGY
```
    Defines the "global" strategy to use for handling HQL and Criteria mutation queries. Specifies a SqmMultiTableMutationStrategy..
    
    See Also:
    
    Constant Field Values
  - QUERY_MULTI_TABLE_INSERT_STRATEGY
```
static final String QUERY_MULTI_TABLE_INSERT_STRATEGY
```
    Defines the "global" strategy to use for handling HQL and Criteria insert queries. Specifies a SqmMultiTableInsertStrategy.
    
    See Also:
    
    Constant Field Values
  - QUERY_STARTUP_CHECKING
```
static final String QUERY_STARTUP_CHECKING
```
    When enabled, specifies that named queries be checked during startup.
    By default, named queries are checked at startup.
    Mainly intended for use in test environments.
    
    See Also:
    
    Constant Field Values
  - ORDER_UPDATES
```
static final String ORDER_UPDATES
```
    Enable ordering of update statements by primary key value.
    
    See Also:
    
    Constant Field Values
  - ORDER_INSERTS
```
static final String ORDER_INSERTS
```
    Enable ordering of insert statements for the purpose of more efficient JDBC batching.
    
    See Also:
    
    Constant Field Values
  - JPA_CALLBACKS_ENABLED
```
static final String JPA_CALLBACKS_ENABLED
```
    JPA callbacks are enabled by default. Set this to false to disable them. Mostly useful to save a bit of memory when they are not used. Experimental and will likely be removed as soon as the memory overhead is resolved.
    
    Since:
    
    5.4
    
    See Also:
    
    CallbackType, Constant Field Values
  - DEFAULT_NULL_ORDERING
```
static final String DEFAULT_NULL_ORDERING
```
    Default precedence of null values in ORDER BY clause.
    Supported options: none (default), first, last.
    
    See Also:
    
    Constant Field Values
  - LOG_JDBC_WARNINGS
```
static final String LOG_JDBC_WARNINGS
```
    When enabled, specifies that JDBC statement warnings should be logged.
    The default is determined by Dialect.isJdbcLogWarningsEnabledByDefault().
    
    Since:
    
    5.1
    
    See Also:
    
    Statement.getWarnings(), Constant Field Values
  - BEAN_CONTAINER
```
static final String BEAN_CONTAINER
```
    Identifies a BeanContainer to be used.
    Note that for CDI-based containers setting this is not necessary - simply pass the BeanManager to use via CDI_BEAN_MANAGER and optionally specify DELAY_CDI_ACCESS. This setting useful to integrate non-CDI bean containers such as Spring.
    
    Since:
    
    5.3
    
    See Also:
    
    Constant Field Values
  - DELAY_CDI_ACCESS
```
static final String DELAY_CDI_ACCESS
```
    Used in conjunction with "hibernate.resource.beans.container" when CDI is used.
    By default, to be JPA spec compliant, Hibernate should access the CDI BeanManager while bootstrapping the SessionFactory. In some cases however this can lead to a chicken/egg situation where the JPA provider immediately accesses the BeanManager when managed beans are awaiting JPA PU injection.
    This setting tells Hibernate to delay accessing until first use.
    This setting has the decided downside that bean config problems will not be done at deployment time, but will instead manifest at runtime. For this reason, the preferred means for supplying a CDI BeanManager is to provide an implementation of ExtendedBeanManager which gives Hibernate a callback when the BeanManager is ready for use.
    
    Since:
    
    5.0.8
    
    See Also:
    
    Constant Field Values
  - C3P0_CONFIG_PREFIX
```
static final String C3P0_CONFIG_PREFIX
```
    A setting prefix used to indicate settings that target the hibernate-c3p0 integration
    
    See Also:
    
    Constant Field Values
  - C3P0_MAX_SIZE
```
static final String C3P0_MAX_SIZE
```
    Maximum size of C3P0 connection pool
    
    See Also:
    
    Constant Field Values
  - C3P0_MIN_SIZE
```
static final String C3P0_MIN_SIZE
```
    Minimum size of C3P0 connection pool
    
    See Also:
    
    Constant Field Values
  - C3P0_TIMEOUT
```
static final String C3P0_TIMEOUT
```
    Maximum idle time for C3P0 connection pool
    
    See Also:
    
    Constant Field Values
  - C3P0_MAX_STATEMENTS
```
static final String C3P0_MAX_STATEMENTS
```
    Maximum size of C3P0 statement cache
    
    See Also:
    
    Constant Field Values
  - C3P0_ACQUIRE_INCREMENT
```
static final String C3P0_ACQUIRE_INCREMENT
```
    Number of connections acquired when pool is exhausted
    
    See Also:
    
    Constant Field Values
  - C3P0_IDLE_TEST_PERIOD
```
static final String C3P0_IDLE_TEST_PERIOD
```
    Idle time before a C3P0 pooled connection is validated
    
    See Also:
    
    Constant Field Values
  - PROXOOL_CONFIG_PREFIX
```
static final String PROXOOL_CONFIG_PREFIX
```
    A setting prefix used to indicate settings that target the hibernate-proxool integration
    
    See Also:
    
    Constant Field Values
  - PROXOOL_XML
```
static final String PROXOOL_XML
```
    Proxool property to configure the Proxool provider using an XML (/path/to/file.xml)
    
    See Also:
    
    Constant Field Values
  - PROXOOL_PROPERTIES
```
static final String PROXOOL_PROPERTIES
```
    Proxool property to configure the Proxool provider using a properties file (/path/to/proxool.properties)
    
    See Also:
    
    Constant Field Values
  - PROXOOL_EXISTING_POOL
```
static final String PROXOOL_EXISTING_POOL
```
    Proxool property to configure the Proxool Provider from an already existing pool (true / false)
    
    See Also:
    
    Constant Field Values
  - PROXOOL_POOL_ALIAS
```
static final String PROXOOL_POOL_ALIAS
```
    Proxool property with the Proxool pool alias to use (Required for PROXOOL_EXISTING_POOL, PROXOOL_PROPERTIES, or PROXOOL_XML)
    
    See Also:
    
    Constant Field Values
  - CACHE_REGION_FACTORY
```
static final String CACHE_REGION_FACTORY
```
    The RegionFactory implementation, either:
    
    an instance of RegionFactory,
    a Class implementing RegionFactory, or
    he name of a class implementing RegionFactory.
    See Also:
    
    Constant Field Values
  - CACHE_KEYS_FACTORY
```
@Deprecated
static final String CACHE_KEYS_FACTORY
```
    Deprecated.
    this is only honored for hibernate-infinispan
    Specifies the CacheKeysFactory to use, either:
    
    an instance of CacheKeysFactory,
    a Class implementing CacheKeysFactory,
    the name of a class implementing CacheKeysFactory,
    "default" as a short name for DefaultCacheKeysFactory, or
    '"simple" as a short name for SimpleCacheKeysFactory.
    Since:
    
    5.2
    
    See Also:
    
    Constant Field Values
  - USE_SECOND_LEVEL_CACHE
```
static final String USE_SECOND_LEVEL_CACHE
```
    When enabled, specifies that the second-level cache may be used.
    By default, if the configured RegionFactory is not the NoCachingRegionFactory, then the second-level cache is enabled. Otherwise, the second-level cache is disabled.
    
    See Also:
    
    Constant Field Values
  - USE_QUERY_CACHE
```
static final String USE_QUERY_CACHE
```
    Enable the query cache (disabled by default).
    
    See Also:
    
    Constant Field Values
  - QUERY_CACHE_FACTORY
```
static final String QUERY_CACHE_FACTORY
```
    Specifies the TimestampsCacheFactory to use.
    
    See Also:
    
    Constant Field Values
  - CACHE_REGION_PREFIX
```
static final String CACHE_REGION_PREFIX
```
    The CacheProvider region name prefix
    
    See Also:
    
    Constant Field Values
  - USE_MINIMAL_PUTS
```
static final String USE_MINIMAL_PUTS
```
    Optimize interaction with the second-level cache to minimize writes, at the cost of more frequent database reads.
    
    See Also:
    
    Constant Field Values
  - USE_STRUCTURED_CACHE
```
static final String USE_STRUCTURED_CACHE
```
    Enables the use of structured second-level cache entries.
    
    See Also:
    
    Constant Field Values
  - AUTO_EVICT_COLLECTION_CACHE
```
static final String AUTO_EVICT_COLLECTION_CACHE
```
    Enables the automatic eviction of a bidirectional association's collection cache when an element in the ManyToOne collection is added, updated, or removed without properly managing the change on the OneToMany side.
    
    See Also:
    
    Constant Field Values
  - USE_DIRECT_REFERENCE_CACHE_ENTRIES
```
static final String USE_DIRECT_REFERENCE_CACHE_ENTRIES
```
    Enable direct storage of entity references into the second level cache when applicable. This is appropriate only for immutable entities.
    By default, entities are always stored in a "disassembled" form.
    
    See Also:
    
    Constant Field Values
  - GLOBALLY_QUOTED_IDENTIFIERS
```
static final String GLOBALLY_QUOTED_IDENTIFIERS
```
    When enabled, all database identifiers are quoted.
    
    See Also:
    
    Constant Field Values
  - GLOBALLY_QUOTED_IDENTIFIERS_SKIP_COLUMN_DEFINITIONS
```
static final String GLOBALLY_QUOTED_IDENTIFIERS_SKIP_COLUMN_DEFINITIONS
```
    Assuming GLOBALLY_QUOTED_IDENTIFIERS, this allows global quoting to skip column definitions defined by Column, JoinColumn, etc.
    JPA states that column definitions are subject to global quoting, so by default this setting is false for JPA compliance. Set to true to avoid explicit column names being quoted due to global quoting (they will still be quoted if explicitly quoted in the annotation or XML).
    
    See Also:
    
    Constant Field Values
  - CHECK_NULLABILITY
```
static final String CHECK_NULLABILITY
```
    Enable nullability checking, raises an exception if an attribute marked as not null is null at runtime.
    Defaults to disabled if Bean Validation is present in the classpath and annotations are used, or enabled otherwise.
    
    See Also:
    
    Constant Field Values
  - BYTECODE_PROVIDER
```
static final String BYTECODE_PROVIDER
```
    Selects a bytecode enhancment library.
    At present only bytebuddy is supported, bytebuddy being the default since version 5.3.
    
    See Also:
    
    Constant Field Values
  - JPAQL_STRICT_COMPLIANCE
```
static final String JPAQL_STRICT_COMPLIANCE
```
    See Also:
    
    Constant Field Values
  - PREFERRED_POOLED_OPTIMIZER
```
static final String PREFERRED_POOLED_OPTIMIZER
```
    When a generator specifies an increment-size and an optimizer was not explicitly specified, which of the "pooled" optimizers should be preferred? Can specify an optimizer short name or the name of a class which implements Optimizer.
    
    See Also:
    
    Constant Field Values
  - QUERY_PLAN_CACHE_ENABLED
```
static final String QUERY_PLAN_CACHE_ENABLED
```
    When enabled, specifies that query plans should be cached.
    By default, the query plan cache is disabled, unless one of the configuration properties "hibernate.query.plan_cache_max_size" or "hibernate.query.plan_parameter_metadata_max_size" is set.
    
    See Also:
    
    Constant Field Values
  - QUERY_PLAN_CACHE_MAX_SIZE
```
static final String QUERY_PLAN_CACHE_MAX_SIZE
```
    The maximum number of entries in the query plan cache or query interpretation cache.
    The default maximum is 2048.
    
    See Also:
    
    QueryPlanCache, Constant Field Values
  - QUERY_PLAN_CACHE_PARAMETER_METADATA_MAX_SIZE
```
@Deprecated(since="6.0")
static final String QUERY_PLAN_CACHE_PARAMETER_METADATA_MAX_SIZE
```
    Deprecated.
    this setting is not currently used
    
    The maximum number of ParameterMetadata instances maintained by the QueryInterpretationCache.
    The default maximum is 128.
    
    See Also:
    
    Constant Field Values
  - NON_CONTEXTUAL_LOB_CREATION
```
static final String NON_CONTEXTUAL_LOB_CREATION
```
    When enabled, specifies that Hibernate should not use contextual LOB creation.
    
    See Also:
    
    LobCreator, LobCreationContext, Constant Field Values
  - HBM2DDL_AUTO
```
static final String HBM2DDL_AUTO
```
    Setting to perform SchemaManagementTool actions automatically as part of the SessionFactory lifecycle. Valid options are enumeratd by Action.
    Interpreted in combination with HBM2DDL_DATABASE_ACTION and HBM2DDL_SCRIPTS_ACTION. If no value is specified, the default is "none".
    
    See Also:
    
    Action, Constant Field Values
  - HBM2DDL_DATABASE_ACTION
```
@Deprecated
static final String HBM2DDL_DATABASE_ACTION
```
    Deprecated.
    Use JAKARTA_HBM2DDL_SCRIPTS_ACTION instead
    
    See Also:
    
    Constant Field Values
  - HBM2DDL_SCRIPTS_ACTION
```
@Deprecated
static final String HBM2DDL_SCRIPTS_ACTION
```
    Deprecated.
    Use JAKARTA_HBM2DDL_SCRIPTS_ACTION instead
    
    See Also:
    
    Constant Field Values
  - HBM2DDL_CONNECTION
```
@Deprecated
static final String HBM2DDL_CONNECTION
```
    Deprecated.
    Use JAKARTA_HBM2DDL_CONNECTION instead
    
    See Also:
    
    Constant Field Values
  - HBM2DDL_CREATE_SOURCE
```
static final String HBM2DDL_CREATE_SOURCE
```
    Specifies whether schema generation commands for schema creation are to be determined based on object/relational mapping metadata, DDL scripts, or a combination of the two. See SourceType for the list of legal values.
    If no value is specified, a default is inferred as follows:
    
    if source scripts are specified via "javax.persistence.schema-generation.create-script-source", then "script" is assumed, or
    otherwise, "metadata" is assumed.
    See Also:
    
    SourceType, Constant Field Values
  - HBM2DDL_DROP_SOURCE
```
static final String HBM2DDL_DROP_SOURCE
```
    Specifies whether schema generation commands for schema dropping are to be determined based on object/relational mapping metadata, DDL scripts, or a combination of the two. See SourceType for the list of legal values.
    If no value is specified, a default is inferred as follows:
    
    if source scripts are specified via "javax.persistence.schema-generation.drop-script-source", then "script" is assumed, or
    otherwise, "metadata" is assumed.
    See Also:
    
    SourceType, Constant Field Values
  - HBM2DDL_CREATE_SCRIPT_SOURCE
```
static final String HBM2DDL_CREATE_SCRIPT_SOURCE
```
    Specifies the CREATE script file as either a Reader configured for reading the DDL script file or a string designating a file URL for the DDL script.
    Hibernate historically also accepted HBM2DDL_IMPORT_FILES for a similar purpose. This setting is now preferred.
    
    See Also:
    
    HBM2DDL_CREATE_SOURCE, HBM2DDL_IMPORT_FILES, Constant Field Values
  - HBM2DDL_DROP_SCRIPT_SOURCE
```
static final String HBM2DDL_DROP_SCRIPT_SOURCE
```
    Specifies the DROP script file as either a Reader configured for reading the DDL script file or a string designating a file URL for the DDL script.
    
    See Also:
    
    HBM2DDL_DROP_SOURCE, Constant Field Values
  - HBM2DDL_SCRIPTS_CREATE_TARGET
```
static final String HBM2DDL_SCRIPTS_CREATE_TARGET
```
    For cases where the "javax.persistence.schema-generation.scripts.action" value indicates that schema creation commands should be written to DDL script file, "javax.persistence.schema-generation.scripts.create-target" specifies either a Writer configured for output of the DDL script or a string specifying the file URL for the DDL script.
    
    See Also:
    
    HBM2DDL_SCRIPTS_ACTION, Constant Field Values
  - HBM2DDL_SCRIPTS_CREATE_APPEND
```
static final String HBM2DDL_SCRIPTS_CREATE_APPEND
```
    For cases where the "javax.persistence.schema-generation.scripts.action" value indicates that schema commands should be written to DDL script file, specifies if schema commands should be appended to the end of the file rather than written at the beginning of the file. Values are: true for appending schema commands to the end of the file, false for writing schema commands at the beginning. The default value is true
    
    See Also:
    
    Constant Field Values
  - HBM2DDL_SCRIPTS_DROP_TARGET
```
static final String HBM2DDL_SCRIPTS_DROP_TARGET
```
    For cases where the "javax.persistence.schema-generation.scripts.action" value indicates that schema drop commands should be written to DDL script file, "javax.persistence.schema-generation.scripts.drop-target" specifies either a Writer configured for output of the DDL script or a string specifying the file URL for the DDL script.
    
    See Also:
    
    HBM2DDL_SCRIPTS_ACTION, Constant Field Values
  - HBM2DDL_IMPORT_FILES
```
static final String HBM2DDL_IMPORT_FILES
```
    Specifies a comma-separated list of file names of scripts containing SQL DML statements that should be executed after schema export completes. The order of the scripts is significant, with the first script in the list being executed first.
    The scripts are only executed if the schema is created by Hibernate, that is, if "hibernate.hbm2ddl.auto" is set to create or create-drop.
    The default value is /import.sql.
    The JPA-standard setting HBM2DDL_CREATE_SCRIPT_SOURCE is now preferred.
    
    See Also:
    
    Constant Field Values
  - HBM2DDL_LOAD_SCRIPT_SOURCE
```
@Deprecated
static final String HBM2DDL_LOAD_SCRIPT_SOURCE
```
    Deprecated.
    Use JAKARTA_HBM2DDL_LOAD_SCRIPT_SOURCE instead
    
    See Also:
    
    Constant Field Values
  - HBM2DDL_IMPORT_FILES_SQL_EXTRACTOR
```
static final String HBM2DDL_IMPORT_FILES_SQL_EXTRACTOR
```
    Reference to the SqlScriptCommandExtractor implementation class to use for parsing source/import files as defined by HBM2DDL_CREATE_SCRIPT_SOURCE, HBM2DDL_DROP_SCRIPT_SOURCE or HBM2DDL_IMPORT_FILES.
    Reference may refer to an instance, a Class object representing a class that implements ImportSqlCommandExtractor, or the name of a class that implements ImportSqlCommandExtractor.
    The default value is SingleLineSqlScriptExtractor.
    
    See Also:
    
    Constant Field Values
  - HBM2DDL_CREATE_NAMESPACES
```
static final String HBM2DDL_CREATE_NAMESPACES
```
    Specifies whether to automatically create also the database schema/catalog. The default is false.
    
    Since:
    
    5.0
    
    See Also:
    
    Constant Field Values
  - HBM2DDL_CREATE_SCHEMAS
```
@Deprecated
static final String HBM2DDL_CREATE_SCHEMAS
```
    Deprecated.
    Use JAKARTA_HBM2DDL_CREATE_SCHEMAS instead
    
    See Also:
    
    Constant Field Values
  - JAKARTA_HBM2DDL_DATABASE_ACTION
```
static final String JAKARTA_HBM2DDL_DATABASE_ACTION
```
    Specifies what type of schema tooling action should be performed against the database specified using either "jakarta.persistence.schema-generation-connection" or the configured ConnectionProvider for the SessionFactory.
    Valid options are enumerated by Action.
    This setting takes precedence over "hibernate.hbm2ddl.auto".
    If no value is specified, the default is "none".
    
    See Also:
    
    Action, JAKARTA_HBM2DDL_CONNECTION, JAKARTA_JDBC_URL, Constant Field Values
  - JAKARTA_HBM2DDL_SCRIPTS_ACTION
```
static final String JAKARTA_HBM2DDL_SCRIPTS_ACTION
```
    Specifies what type of schema tooling action should be written to script files.
    Valid options are enumerated by Action.
    The script file is identified using "jakarta.persistence.schema-generation.scripts.create-target".
    If no value is specified, the default is "none".
    
    See Also:
    
    Action, JAKARTA_HBM2DDL_SCRIPTS_CREATE_TARGET, JAKARTA_HBM2DDL_SCRIPTS_DROP_TARGET, Constant Field Values
  - JAKARTA_HBM2DDL_CONNECTION
```
static final String JAKARTA_HBM2DDL_CONNECTION
```
    Allows passing a specific Connection instance to be used by SchemaManagementTool for the purpose of determining the Dialect, and for performing {@value #JAKARTA_HBM2DDL_DATABASE_ACTION database actions} if requested.
    For Dialect resolution, "jakarta.persistence.database-product-name" and, optionally, "jakarta.persistence.database-product-version", "jakarta.persistence.database-major-version", and "jakarta.persistence.database-minor-version" can be used instead
    
    See Also:
    
    JAKARTA_HBM2DDL_DB_NAME, JAKARTA_HBM2DDL_DB_VERSION, JAKARTA_HBM2DDL_DB_MAJOR_VERSION, JAKARTA_HBM2DDL_DB_MINOR_VERSION, Constant Field Values
  - JAKARTA_HBM2DDL_DB_NAME
```
static final String JAKARTA_HBM2DDL_DB_NAME
```
    Specifies the name of the database vendor (as would be reported by DatabaseMetaData.getDatabaseProductName()) for the purpose of determining the Dialect to use.
    For cases when the name of the database vendor is not enough alone, a combination of "jakarta.persistence.database-product-version", "jakarta.persistence.database-major-version" "jakarta.persistence.database-minor-version" can be used instead
    
    See Also:
    
    JAKARTA_HBM2DDL_DB_VERSION, JAKARTA_HBM2DDL_DB_MAJOR_VERSION, JAKARTA_HBM2DDL_DB_MINOR_VERSION, Constant Field Values
    
    "Implementation Specification:"
    
    {@value #JAKARTA_HBM2DDL_DATABASE_ACTION database actions} are not available when supplying just the name and versions
  - JAKARTA_HBM2DDL_DB_VERSION
```
static final String JAKARTA_HBM2DDL_DB_VERSION
```
    Used in conjunction with "jakarta.persistence.database-product-name" for the purpose of determining the Dialect to use when the name does not provide enough detail.
    The value is expected to match what would be returned from DatabaseMetaData.getDatabaseProductVersion()) for the underlying database.
    
    See Also:
    
    JAKARTA_HBM2DDL_DB_NAME, Constant Field Values
  - JAKARTA_HBM2DDL_DB_MAJOR_VERSION
```
static final String JAKARTA_HBM2DDL_DB_MAJOR_VERSION
```
    Used in conjunction with "jakarta.persistence.database-product-name" for the purpose of determining the Dialect to use when the name does not provide enough detail.
    The value is expected to match what would be returned from DatabaseMetaData.getDatabaseMajorVersion()) for the underlying database.
    
    See Also:
    
    JAKARTA_HBM2DDL_DB_NAME, Constant Field Values
  - JAKARTA_HBM2DDL_DB_MINOR_VERSION
```
static final String JAKARTA_HBM2DDL_DB_MINOR_VERSION
```
    Used in conjunction with "jakarta.persistence.database-product-name" for the purpose of determining the Dialect to use when the name does not provide enough detail.
    The value is expected to match what would be returned from DatabaseMetaData.getDatabaseMinorVersion()) for the underlying database.
    
    See Also:
    
    JAKARTA_HBM2DDL_DB_NAME, Constant Field Values
  - JAKARTA_HBM2DDL_CREATE_SOURCE
```
static final String JAKARTA_HBM2DDL_CREATE_SOURCE
```
    Specifies whether schema generation commands for schema creation are to be determined based on object/relational mapping metadata, DDL scripts, or a combination of the two. See SourceType for the list of legal values.
    If no value is specified, a default is inferred as follows:
    
    if source scripts are specified via "javax.persistence.schema-generation.create-script-source", then "script" is assumed, or
    otherwise, "metadata" is assumed.
    See Also:
    
    SourceType, Constant Field Values
  - JAKARTA_HBM2DDL_DROP_SOURCE
```
static final String JAKARTA_HBM2DDL_DROP_SOURCE
```
    Specifies whether schema generation commands for schema dropping are to be determined based on object/relational mapping metadata, DDL scripts, or a combination of the two. See SourceType for the list of legal values.
    If no value is specified, a default is inferred as follows:
    
    if source scripts are specified via "javax.persistence.schema-generation.drop-script-source", then "script" is assumed, or
    otherwise, "metadata" is assumed.
    See Also:
    
    SourceType, Constant Field Values
  - JAKARTA_HBM2DDL_CREATE_SCRIPT_SOURCE
```
static final String JAKARTA_HBM2DDL_CREATE_SCRIPT_SOURCE
```
    Specifies the CREATE script file as either a Reader configured for reading the DDL script file or a string designating a file URL for the DDL script.
    Hibernate historically also accepted HBM2DDL_IMPORT_FILES for a similar purpose. This setting is now preferred.
    
    See Also:
    
    HBM2DDL_CREATE_SOURCE, HBM2DDL_IMPORT_FILES, Constant Field Values
  - JAKARTA_HBM2DDL_DROP_SCRIPT_SOURCE
```
static final String JAKARTA_HBM2DDL_DROP_SCRIPT_SOURCE
```
    Specifies the DROP script file as either a Reader configured for reading the DDL script file or a string designating a file URL for the DDL script.
    
    See Also:
    
    HBM2DDL_DROP_SOURCE, Constant Field Values
  - JAKARTA_HBM2DDL_SCRIPTS_CREATE_TARGET
```
static final String JAKARTA_HBM2DDL_SCRIPTS_CREATE_TARGET
```
    For cases where "jakarta.persistence.schema-generation.scripts.action" indicates that schema creation commands should be written to a script file, this setting specifies either a Writer configured for output of the DDL script or a string specifying the file URL for the DDL script.
    
    See Also:
    
    JAKARTA_HBM2DDL_SCRIPTS_ACTION, Constant Field Values
  - JAKARTA_HBM2DDL_SCRIPTS_DROP_TARGET
```
static final String JAKARTA_HBM2DDL_SCRIPTS_DROP_TARGET
```
    For cases where "jakarta.persistence.schema-generation.scripts.action" indicates that schema drop commands should be written to a script file, this setting specifies either a Writer configured for output of the DDL script or a string specifying the file URL for the DDL script.
    
    See Also:
    
    JAKARTA_HBM2DDL_SCRIPTS_ACTION, Constant Field Values
  - JAKARTA_HBM2DDL_LOAD_SCRIPT_SOURCE
```
static final String JAKARTA_HBM2DDL_LOAD_SCRIPT_SOURCE
```
    JPA-standard variant of HBM2DDL_IMPORT_FILES for specifying a database initialization script to be run as part of schema-export Specifies a Reader configured for reading of the SQL load script or a string designating the URL for the SQL load script.
    
    See Also:
    
    Constant Field Values
  - JAKARTA_HBM2DDL_CREATE_SCHEMAS
```
static final String JAKARTA_HBM2DDL_CREATE_SCHEMAS
```
    The JPA variant of HBM2DDL_CREATE_NAMESPACES used to specify whether database schemas used in the mapping model should be created on export in addition to creating the tables, sequences, etc. The default is false, meaning to not create schemas
    
    See Also:
    
    Constant Field Values
  - HBM2DDL_FILTER_PROVIDER
```
static final String HBM2DDL_FILTER_PROVIDER
```
    Used to specify the SchemaFilterProvider to be used by create, drop, migrate and validate operations on the database schema. A SchemaFilterProvider provides filters that can be used to limit the scope of these operations to specific namespaces, tables and sequences. All objects are included by default.
    
    Since:
    
    5.1
    
    See Also:
    
    Constant Field Values
  - HBM2DDL_JDBC_METADATA_EXTRACTOR_STRATEGY
```
static final String HBM2DDL_JDBC_METADATA_EXTRACTOR_STRATEGY
```
    Setting to choose the strategy used to access the JDBC Metadata.
    Valid options are defined by JdbcMetadaAccessStrategy. JdbcMetadaAccessStrategy.GROUPED is the default.
    
    See Also:
    
    JdbcMetadaAccessStrategy, Constant Field Values
  - HBM2DDL_DELIMITER
```
static final String HBM2DDL_DELIMITER
```
    Identifies the delimiter to use to separate schema management statements in script outputs.
    The default value is ;.
    
    See Also:
    
    Constant Field Values
  - HBM2DDL_CHARSET_NAME
```
static final String HBM2DDL_CHARSET_NAME
```
    The name of the charset used by the schema generation resource.
    By default, the JVM default charset is used.
    
    Since:
    
    5.2.3
    
    See Also:
    
    Constant Field Values
  - HBM2DDL_HALT_ON_ERROR
```
static final String HBM2DDL_HALT_ON_ERROR
```
    When enabled, specifies that the schema migration tool should halt on any error, terminating the bootstrap process.
    
    Since:
    
    5.2.4
    
    See Also:
    
    Constant Field Values
  - HBM2DDL_DEFAULT_CONSTRAINT_MODE
```
static final String HBM2DDL_DEFAULT_CONSTRAINT_MODE
```
    Used with the ConstraintMode.PROVIDER_DEFAULT strategy for foreign key mapping.
    Valid values are ConstraintMode.CONSTRAINT and ConstraintMode.NO_CONSTRAINT.
    The default value is ConstraintMode.CONSTRAINT.
    
    Since:
    
    5.4
    
    See Also:
    
    Constant Field Values
  - CUSTOM_ENTITY_DIRTINESS_STRATEGY
```
static final String CUSTOM_ENTITY_DIRTINESS_STRATEGY
```
    Setting to identify a CustomEntityDirtinessStrategy to use. May specify either a class name or an instance.
    
    See Also:
    
    Constant Field Values
  - USE_ENTITY_WHERE_CLAUSE_FOR_COLLECTIONS
```
static final String USE_ENTITY_WHERE_CLAUSE_FOR_COLLECTIONS
```
    The Where annotation specifies a restriction on the table rows which are visible as entity class instances or collection elements.
    This setting controls whether the restriction is applied when loading a one-to-many or or many-to-many association whose target type defines the restriction.
    By default, the restriction is not applied. When this setting is enabled, the restriction is applied.
    The setting has no effect on a collection of embeddable values containing a many-to-one association to the entity.
    
    See Also:
    
    Constant Field Values
  - MULTI_TENANT_CONNECTION_PROVIDER
```
static final String MULTI_TENANT_CONNECTION_PROVIDER
```
    Specifies a MultiTenantConnectionProvider to use. Since MultiTenantConnectionProvider is also a service, it may be configured directly via the StandardServiceRegistryBuilder.
    
    Since:
    
    4.1
    
    See Also:
    
    Constant Field Values
  - MULTI_TENANT_IDENTIFIER_RESOLVER
```
static final String MULTI_TENANT_IDENTIFIER_RESOLVER
```
    Specifies a CurrentTenantIdentifierResolver to use, either:
    
    an instance of CurrentTenantIdentifierResolver,
    a Class representing an class that implements CurrentTenantIdentifierResolver, or
    the name of a class that implements CurrentTenantIdentifierResolver.
    Since:
    
    4.1
    
    See Also:
    
    Constant Field Values
  - INTERCEPTOR
```
static final String INTERCEPTOR
```
    Specifies an Interceptor implementation associated with the SessionFactory and propagated to each Session created from the SessionFactory. Either:
    
    an instance of Interceptor,
    a Class representing a class that implements Interceptor, or
    the name of a class that implements Interceptor.
    This setting identifies an Interceptor which is effectively a singleton across all the sessions opened from the SessionFactory to which it is applied; the same instance will be passed to each Session. If there should be a separate instance of Interceptor for each Session, use SESSION_SCOPED_INTERCEPTOR instead.
    Since:
    
    5.0
    
    See Also:
    
    Constant Field Values
  - SESSION_SCOPED_INTERCEPTOR
```
static final String SESSION_SCOPED_INTERCEPTOR
```
    Specifies an Interceptor implementation associated with the SessionFactory and propagated to each Session created from the SessionFactory. Either:
    
    a Class representing a class that implements Interceptor,
    the name of a class that implements Interceptor, or
    an instance of Supplier used to obtain the interceptor.
    Note that this setting cannot specify an Interceptor instance.
    This setting identifies an Interceptor implementation that is to be applied to every Session opened from the SessionFactory, but unlike INTERCEPTOR, a separate instance created for each Session.
    Since:
    
    5.2
    
    See Also:
    
    Constant Field Values
  - STATEMENT_INSPECTOR
```
static final String STATEMENT_INSPECTOR
```
    Specifies a StatementInspector implementation associated with the SessionFactory, either:
    
    an instance of StatementInspector,
    a Class representing an class that implements StatementInspector, or
    the name of a class that implements StatementInspector.
    Since:
    
    5.0
    
    See Also:
    
    Constant Field Values
  - ENABLE_LAZY_LOAD_NO_TRANS
```
static final String ENABLE_LAZY_LOAD_NO_TRANS
```
    See Also:
    
    Constant Field Values
  - BATCH_FETCH_STYLE
```
@Deprecated(since="6.0")
static final String BATCH_FETCH_STYLE
```
    Deprecated.
    An appropriate batch-fetch style is selected automatically
    
    Specifies the BatchFetchStyle to use, either the name of a {code BatchFetchStyle} instance, or an instance of BatchFetchStyle.
    
    See Also:
    
    Constant Field Values
  - DELAY_ENTITY_LOADER_CREATIONS
```
static final String DELAY_ENTITY_LOADER_CREATIONS
```
    Controls how entity loaders are created.
    When true, the default, the loaders are only created on first access; this ensures that all access patterns which are not useful to the application are never instantiated, possibly saving a substantial amount of memory for applications having many entities. The only exception is the loader for LockMode.NONE, which will always be eagerly initialized; this is necessary to detect mapping errors.
    false indicates that all loaders should be created up front; this will consume more memory but ensures all necessary memory is allocated right away.
    
    Since:
    
    5.3
    
    See Also:
    
    Constant Field Values
  - JTA_TRACK_BY_THREAD
```
static final String JTA_TRACK_BY_THREAD
```
    A transaction can be rolled back by another thread ("tracking by thread") -- not the original application. Examples of this include a JTA transaction timeout handled by a background reaper thread. The ability to handle this situation requires checking the Thread ID every time Session is called. This can certainly have performance considerations. Default is true (enabled).
    
    See Also:
    
    Constant Field Values
  - ENABLE_SYNONYMS
```
static final String ENABLE_SYNONYMS
```
    If enabled, allows schema update and validation to support synonyms. Due to the possibility that this would return duplicate tables (especially in Oracle), this is disabled by default.
    
    See Also:
    
    Constant Field Values
  - EXTRA_PHYSICAL_TABLE_TYPES
```
static final String EXTRA_PHYSICAL_TABLE_TYPES
```
    Specifies a comma-separated list of extra table types, in addition to the default types "TABLE" and "VIEW", to recognize as physical tables when performing schema update, creation and validation.
    
    Since:
    
    5.0
    
    See Also:
    
    Constant Field Values
  - UNIQUE_CONSTRAINT_SCHEMA_UPDATE_STRATEGY
```
static final String UNIQUE_CONSTRAINT_SCHEMA_UPDATE_STRATEGY
```
    Unique columns and unique keys both use unique constraints in most dialects. The schema exporter must create these constraints, but database support for finding existing constraints is extremely inconsistent. Worse, unique constraints without explicit names are assigned names with randomly generated characters.
    Therefore, select from these strategies:
    
    DROP_RECREATE_QUIETLY: Attempt to drop, then (re-)create each unique constraint, ignoring any exceptions thrown. This is the default.
    RECREATE_QUIETLY: attempt to (re-)create unique constraints, ignoring exceptions thrown if the constraint already existed.
    SKIP: do not attempt to create unique constraints on a schema update.
    See Also:
    
    Constant Field Values
  - GENERATE_STATISTICS
```
static final String GENERATE_STATISTICS
```
    When enabled, specifies that statistics should be collected.
    
    See Also:
    
    Constant Field Values
  - LOG_SESSION_METRICS
```
static final String LOG_SESSION_METRICS
```
    Controls whether session metrics should be logged for any session in which statistics are being collected.
    By default, logging of session metrics is disabled unless GENERATE_STATISTICS is enabled.
    
    See Also:
    
    Constant Field Values
  - LOG_SLOW_QUERY
```
static final String LOG_SLOW_QUERY
```
    Specifies a duration in milliseconds defining the minimum query execution time that characterizes a "slow" query. Any SQL query which takes longer than this amount of time to execute will be logged.
    A value of 0, the default, disables logging of "slow" queries.
    
    See Also:
    
    Constant Field Values
  - AUTO_SESSION_EVENTS_LISTENER
```
static final String AUTO_SESSION_EVENTS_LISTENER
```
    Defines a default SessionEventListener to be applied to newly-opened Sessions.
    
    See Also:
    
    Constant Field Values
  - CREATE_EMPTY_COMPOSITES_ENABLED
```
static final String CREATE_EMPTY_COMPOSITES_ENABLED
```
    [EXPERIMENTAL] Enable instantiation of composite/embedded objects when all attribute values are null. The default (and historical) behavior is that a null reference will be used to represent the composite when all of its attributes are null.
    This is an experimental feature that has known issues. It should not be used in production until it is stabilized. See Hibernate JIRA issue HHH-11936 for details.
    
    Since:
    
    5.1
    
    See Also:
    
    Constant Field Values
  - ALLOW_JTA_TRANSACTION_ACCESS
```
static final String ALLOW_JTA_TRANSACTION_ACCESS
```
    When enabled, allows access to the Transaction even when using a JTA for transaction management.
    Values are true, which grants access, and false, which does not.
    The default behavior is to allow access unless Hibernate is bootstrapped via JPA.
    
    See Also:
    
    Constant Field Values
  - ALLOW_UPDATE_OUTSIDE_TRANSACTION
```
static final String ALLOW_UPDATE_OUTSIDE_TRANSACTION
```
    When enabled, allows update operations outside a transaction.
    Since version 5.2 Hibernate conforms with the JPA specification and disallows flushing any update outside a transaction.
    Values are true, which allows flushing outside a transaction, and false, which does not.
    The default behavior is to disallow update operations outside a transaction.
    
    Since:
    
    5.2
    
    See Also:
    
    Constant Field Values
  - ALLOW_REFRESH_DETACHED_ENTITY
```
static final String ALLOW_REFRESH_DETACHED_ENTITY
```
    When enabled, allows calls to EntityManager.refresh(Object) and Session.refresh(Object) on a detached entity instance.
    Values are true, which allows refreshing a detached instance and false, which does not. When refreshing is disallowed, an IllegalArgumentException is thrown.
    The default behavior is to allow refreshing a detached instance unless Hibernate is bootstrapped via JPA.
    
    Since:
    
    5.2
    
    See Also:
    
    Constant Field Values
  - MERGE_ENTITY_COPY_OBSERVER
```
static final String MERGE_ENTITY_COPY_OBSERVER
```
    Setting that specifies how Hibernate will respond when multiple representations of the same persistent entity ("entity copy") are detected while merging.
    The possible values are:
    
    disallow (the default): throws IllegalStateException if an entity copy is detected
    allow: performs the merge operation on each entity copy that is detected
    log: (provided for testing only) performs the merge operation on each entity copy that is detected and logs information about the entity copies. This setting requires DEBUG logging be enabled for EntityCopyAllowedLoggedObserver.
    Alternatively, the application may customize the behavior by providing an implementation of EntityCopyObserver and setting the property "hibernate.event.merge.entity_copy_observer" to the class name.
    When this property is set to allow or log, Hibernate will merge each entity copy detected while cascading the merge operation. In the process of merging each entity copy, Hibernate will cascade the merge operation from each entity copy to its associations with CascadeType.MERGE or CascadeType.ALL. The entity state resulting from merging an entity copy will be overwritten when another entity copy is merged.
    Since:
    
    4.3
    
    See Also:
    
    Constant Field Values
  - CRITERIA_VALUE_HANDLING_MODE
```
static final String CRITERIA_VALUE_HANDLING_MODE
```
    By default, criteria queries use bind parameters for any value passed via the JPA Criteria API.
    
    The "bind" mode uses bind variables for any literal value.
    The "inline" mode inlines values as SQL literals.
    The default value is ValueHandlingMode.BIND.
    Since:
    
    6.0.0
    
    See Also:
    
    ValueHandlingMode, Constant Field Values
  - JPA_COMPLIANCE
```
static final String JPA_COMPLIANCE
```
    Specifies a default value for all JpaCompliance flags. Each individual flag may still be overridden by explicitly specifying its specific configuration property.
    
    Since:
    
    6.0
    
    See Also:
    
    JPA_TRANSACTION_COMPLIANCE, JPA_QUERY_COMPLIANCE, JPA_LIST_COMPLIANCE, JPA_ORDER_BY_MAPPING_COMPLIANCE, JPA_CLOSED_COMPLIANCE, JPA_PROXY_COMPLIANCE, JPA_CACHING_COMPLIANCE, JPA_ID_GENERATOR_GLOBAL_SCOPE_COMPLIANCE, JPA_LOAD_BY_ID_COMPLIANCE, Constant Field Values
  - JPA_TRANSACTION_COMPLIANCE
```
static final String JPA_TRANSACTION_COMPLIANCE
```
    When enabled, specifies that the Hibernate Transaction should behave according to the semantics defined by the JPA specification for an EntityTransaction.
    
    Since:
    
    5.3
    
    See Also:
    
    JpaCompliance.isJpaTransactionComplianceEnabled(), Constant Field Values
  - JPA_QUERY_COMPLIANCE
```
static final String JPA_QUERY_COMPLIANCE
```
    When enabled, specifies that every query must strictly follow the specified behavior of Query. The affects JPQL queries, criteria queries, and native SQL queries.
    This setting modifies the behavior of the JPQL query translator, and of the Query interface itself. In particular, it forces all methods of Query to throw the exception types defined by the JPA specification.
    If enabled, any deviations from the JPQL specification results in an exception. Therefore, this setting is not recommended, since it prohibits the use of many useful features of HQL.
    
    Since:
    
    5.3
    
    See Also:
    
    JpaCompliance.isJpaQueryComplianceEnabled(), Constant Field Values
  - JPA_LIST_COMPLIANCE
```
@Deprecated(since="6.0")
static final String JPA_LIST_COMPLIANCE
```
    Deprecated.
    Use DEFAULT_LIST_SEMANTICS instead. The specification is actually undefined in terms of how this should be handled. It actually says that portable applications should not rely on a specific behavior in terms of a List with no `@OrderColumn`
    
    Controls whether Hibernate should recognize what it considers a "bag" (PersistentBag) as a list (PersistentList) or as a bag.
    If enabled, Hibernate will recognize it as a list where the OrderColumn annotation is simply missing (and its defaults will apply).
    
    Since:
    
    5.3
    
    See Also:
    
    JpaCompliance.isJpaListComplianceEnabled(), Constant Field Values
  - JPA_ORDER_BY_MAPPING_COMPLIANCE
```
static final String JPA_ORDER_BY_MAPPING_COMPLIANCE
```
    JPA specifies that items occurring in OrderBy lists must be references to entity attributes, whereas Hibernate, by default, allows more complex expressions.
    If enabled, an exception is thrown for items which are not entity attribute references.
    
    Since:
    
    6.0
    
    See Also:
    
    JpaCompliance.isJpaOrderByMappingComplianceEnabled(), Constant Field Values
  - JPA_CLOSED_COMPLIANCE
```
static final String JPA_CLOSED_COMPLIANCE
```
    JPA specifies that an IllegalStateException must be thrown by EntityManager.close() and EntityManagerFactory.close() if the object has already been closed. By default, Hibernate treats any additional call to close() as a noop.
    When enabled, this setting forces Hibernate to throw an exception if close() is called on an instance that was already closed.
    
    Since:
    
    5.3
    
    See Also:
    
    JpaCompliance.isJpaClosedComplianceEnabled(), Constant Field Values
  - JPA_PROXY_COMPLIANCE
```
static final String JPA_PROXY_COMPLIANCE
```
    The JPA specification insists that an EntityNotFoundException must be thrown whenever an uninitialized entity proxy with no corresponding row in the database is accessed. For most programs, this results in many completely unnecessary round trips to the database.
    Traditionally, Hibernate does not initialize an entity proxy when its identifier attribute is accessed, since the identifier value is already known and held in the proxy instance. This behavior saves the round trip to the database.
    When enabled, this setting forces Hibernate to initialize the entity proxy when its identifier is accessed. Clearly, this setting is not recommended.
    
    Since:
    
    5.2.13
    
    See Also:
    
    JpaCompliance.isJpaProxyComplianceEnabled(), Constant Field Values
  - JPA_CACHING_COMPLIANCE
```
static final String JPA_CACHING_COMPLIANCE
```
    By default, Hibernate uses second-level cache invalidation for entities with secondary tables in order to avoid the possibility of inconsistent cached data in the case where different transactions simultaneously update different table rows corresponding to the same entity instance.
    The JPA TCK, for no good reason, requires that entities with secondary tables be immediately cached in the second-level cache rather than invalidated and re-cached on a subsequent read.
    Note that Hibernate's default behavior here is safer and more careful than the behavior mandated by the TCK but YOLO.
    When enabled, this setting makes Hibernate pass the TCK.
    
    Since:
    
    5.3
    
    See Also:
    
    JpaCompliance.isJpaCacheComplianceEnabled(), AbstractEntityPersister.isCacheInvalidationRequired(), Constant Field Values
  - JPA_ID_GENERATOR_GLOBAL_SCOPE_COMPLIANCE
```
static final String JPA_ID_GENERATOR_GLOBAL_SCOPE_COMPLIANCE
```
    Determines whether the scope of any identifier generator name specified via TableGenerator.name() or SequenceGenerator.name() is considered global to the persistence unit, or local to the entity in which identifier generator is defined.
    If enabled, the name will be considered globally scoped, and so the existence of two different generators with the same name will be considered a collision, and will result in an exception during bootstrap.
    
    Since:
    
    5.2.17
    
    See Also:
    
    JpaCompliance.isGlobalGeneratorScopeEnabled(), Constant Field Values
  - JPA_LOAD_BY_ID_COMPLIANCE
```
static final String JPA_LOAD_BY_ID_COMPLIANCE
```
    Determines if an identifier value passed to EntityManager.find(java.lang.Class<T>, java.lang.Object) or EntityManager.getReference(java.lang.Class<T>, java.lang.Object) may be coerced to the identifier type declared by the entity. For example, an Integer argument might be widened to Long.
    By default, coercion is allowed. When enabled, coercion is disallowed, as required by the JPA specification.
    
    Since:
    
    6.0
    
    See Also:
    
    JpaCompliance.isLoadByIdComplianceEnabled(), Constant Field Values
  - TABLE_GENERATOR_STORE_LAST_USED
```
static final String TABLE_GENERATOR_STORE_LAST_USED
```
    Determines if the identifier value stored in the database table backing a table generator is the last value returned by the identifier generator, or the next value to be returned.
    By default, the value stored in the database table is the last generated value.
    
    Since:
    
    5.3
    
    See Also:
    
    Constant Field Values
  - FAIL_ON_PAGINATION_OVER_COLLECTION_FETCH
```
static final String FAIL_ON_PAGINATION_OVER_COLLECTION_FETCH
```
    When pagination is used in combination with a fetch join applied to a collection or many-valued association, the limit must be applied in-memory instead of on the database. This typically has terrible performance characteristics, and should be avoided.
    When enabled, this setting specifies that an exception should be thrown for any query which would result in the limit being applied in-memory.
    By default, the exception is disabled, and the possibility of terrible performance is left as a problem for the client to avoid.
    
    Since:
    
    5.2.13
    
    See Also:
    
    Constant Field Values
  - IMMUTABLE_ENTITY_UPDATE_QUERY_HANDLING_MODE
```
static final String IMMUTABLE_ENTITY_UPDATE_QUERY_HANDLING_MODE
```
    This setting defines how Immutable entities are handled when executing a bulk update query. Valid options are enumerated by ImmutableEntityUpdateQueryHandlingMode:
    
    "warning" specifies that a warning log message is issued when an immutable entity is to be updated via a bulk update statement, and
    "exception" specifies that a HibernateException should be thrown.
    By default, a warning is logged.
    Since:
    
    5.2.17
    
    See Also:
    
    ImmutableEntityUpdateQueryHandlingMode, Constant Field Values
  - IN_CLAUSE_PARAMETER_PADDING
```
static final String IN_CLAUSE_PARAMETER_PADDING
```
    Determines how parameters occurring in a SQL IN predicate are expanded. By default, the IN predicate expands to include sufficient bind parameters to accommodate the specified arguments.
    However, for database systems supporting execution plan caching, there's a better chance of hitting the cache if the number of possible IN clause parameter list lengths is smaller.
    When this setting is enabled, we expand the number of bind parameters to an integer power of two: 4, 8, 16, 32, 64. Thus, if 5, 6, or 7 arguments are bound to a parameter, a SQL statement with 8 bind parameters in the IN clause will be used, and null will be bound to the left-over parameters.
    
    Since:
    
    5.2.17
    
    See Also:
    
    Constant Field Values
  - QUERY_STATISTICS_MAX_SIZE
```
static final String QUERY_STATISTICS_MAX_SIZE
```
    This setting controls the number of QueryStatistics entries that will be stored by the Hibernate Statistics object.
    The default value is 5000.
    
    Since:
    
    5.4
    
    See Also:
    
    Constant Field Values
  - SEQUENCE_INCREMENT_SIZE_MISMATCH_STRATEGY
```
static final String SEQUENCE_INCREMENT_SIZE_MISMATCH_STRATEGY
```
    This setting defines the SequenceMismatchStrategy used when Hibernate detects a mismatch between a sequence configuration in an entity mapping and its database sequence object counterpart.
    Possible values are SequenceMismatchStrategy.EXCEPTION, SequenceMismatchStrategy.LOG, SequenceMismatchStrategy.FIX and SequenceMismatchStrategy.NONE.
    The default value is SequenceMismatchStrategy.EXCEPTION, meaning that an exception is thrown when such a conflict is detected.
    
    Since:
    
    5.4
    
    See Also:
    
    Constant Field Values
  - PREFERRED_BOOLEAN_JDBC_TYPE_CODE
```
static final String PREFERRED_BOOLEAN_JDBC_TYPE_CODE
```
    Specifies the preferred JDBC type code for storing boolean values. When no type code is explicitly specified, a sensible dialect-specific default type code is used.
    
    Since:
    
    6.0
    
    See Also:
    
    Constant Field Values
  - JSON_FORMAT_MAPPER
```
static final String JSON_FORMAT_MAPPER
```
    Specifies a FormatMapper used for for JSON serialization and deserialization, either:
    
    an instance of FormatMapper,
    a Class representing a class that implements FormatMapper,
    the name of a class that implements FormatMapper, or
    one of the short hand constants jackson or jsonb.
    By default, the first of the possible providers that is available in the runtime is used, according to the listing order.
    Since:
    
    6.0
    
    See Also:
    
    Constant Field Values
  - TIMEZONE_DEFAULT_STORAGE
```
static final String TIMEZONE_DEFAULT_STORAGE
```
    Specifies the default strategy for storage of the timezone information for zoned datetime types:
    
    TimeZoneStorageType.NORMALIZE,
    TimeZoneStorageType.COLUMN,
    TimeZoneStorageType.NATIVE, or
    TimeZoneStorageType.AUTO.
    The default is TimeZoneStorageType.NORMALIZE, meaning that timezone information is not stored by default, but timestamps are normalized to UTC instead.
    Since:
    
    6.0
    
    See Also:
    
    Constant Field Values
  - JPA_PERSISTENCE_PROVIDER
```
@Deprecated
static final String JPA_PERSISTENCE_PROVIDER
```
    Deprecated.
    Use JAKARTA_PERSISTENCE_PROVIDER instead
    
    Specifies a class implementing PersistenceProvider.
    See JPA 2 sections 9.4.3 and 8.2.1.4
    
    See Also:
    
    Constant Field Values
  - JPA_TRANSACTION_TYPE
```
@Deprecated
static final String JPA_TRANSACTION_TYPE
```
    Deprecated.
    Use JAKARTA_TRANSACTION_TYPE instead
    
    The type of transactions supported by the entity managers.
    See JPA 2 sections 9.4.3 and 8.2.1.2
    
    See Also:
    
    Constant Field Values
  - JPA_JTA_DATASOURCE
```
@Deprecated
static final String JPA_JTA_DATASOURCE
```
    Deprecated.
    Use JAKARTA_JTA_DATASOURCE instead
    
    The JNDI name of a JTA DataSource.
    See JPA 2 sections 9.4.3 and 8.2.1.5
    
    See Also:
    
    Constant Field Values
  - JPA_NON_JTA_DATASOURCE
```
@Deprecated
static final String JPA_NON_JTA_DATASOURCE
```
    Deprecated.
    Use JAKARTA_NON_JTA_DATASOURCE instead
    
    The JNDI name of a non-JTA DataSource.
    See JPA 2 sections 9.4.3 and 8.2.1.5
    
    See Also:
    
    Constant Field Values
  - JPA_JDBC_DRIVER
```
@Deprecated
static final String JPA_JDBC_DRIVER
```
    Deprecated.
    Use JAKARTA_JDBC_DRIVER instead
    
    The name of a JDBC driver to use to connect to the database.
    Used in conjunction with JPA_JDBC_URL, JPA_JDBC_USER and JPA_JDBC_PASSWORD to specify how to connect to the database.
    When connections are obtained from a DataSource, use either JPA_JTA_DATASOURCE or JPA_NON_JTA_DATASOURCE instead.
    See section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JPA_JDBC_URL
```
@Deprecated
static final String JPA_JDBC_URL
```
    Deprecated.
    Use JAKARTA_JDBC_URL instead
    
    The JDBC connection URL to use to connect to the database.
    Used in conjunction with JPA_JDBC_DRIVER, JPA_JDBC_USER and JPA_JDBC_PASSWORD to specify how to connect to the database.
    When connections are obtained from a DataSource, use either JPA_JTA_DATASOURCE or JPA_NON_JTA_DATASOURCE instead.
    See section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JPA_JDBC_USER
```
@Deprecated
static final String JPA_JDBC_USER
```
    Deprecated.
    Use JAKARTA_JDBC_USER instead
    
    The database user to use when connecting via JDBC.
    Used in conjunction with JPA_JDBC_DRIVER, JPA_JDBC_URL and JPA_JDBC_PASSWORD to specify how to connect to the database.
    See section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JPA_JDBC_PASSWORD
```
@Deprecated
static final String JPA_JDBC_PASSWORD
```
    Deprecated.
    Use JAKARTA_JDBC_PASSWORD instead
    
    The password to use when connecting via JDBC.
    Used in conjunction with JPA_JDBC_DRIVER, JPA_JDBC_URL and JPA_JDBC_USER to specify how to connect to the database.
    See JPA 2 section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JPA_SHARED_CACHE_MODE
```
@Deprecated
static final String JPA_SHARED_CACHE_MODE
```
    Deprecated.
    Use JAKARTA_SHARED_CACHE_MODE instead
    
    Used to indicate whether second-level (what JPA terms shared cache) caching is enabled as per the rules defined in JPA 2 section 3.1.7.
    See JPA 2 sections 9.4.3 and 8.2.1.7
    
    See Also:
    
    SharedCacheMode, Constant Field Values
  - JPA_SHARED_CACHE_RETRIEVE_MODE
```
@Deprecated
static final String JPA_SHARED_CACHE_RETRIEVE_MODE
```
    Deprecated.
    Use JAKARTA_SHARED_CACHE_RETRIEVE_MODE instead
    
    Used to indicate if the provider should attempt to retrieve requested data in the shared cache.
    
    See Also:
    
    CacheRetrieveMode, Constant Field Values
  - JPA_SHARED_CACHE_STORE_MODE
```
@Deprecated
static final String JPA_SHARED_CACHE_STORE_MODE
```
    Deprecated.
    Use JAKARTA_SHARED_CACHE_STORE_MODE instead
    
    Used to indicate if the provider should attempt to store data loaded from the database in the shared cache.
    
    See Also:
    
    CacheStoreMode, Constant Field Values
  - JPA_VALIDATION_MODE
```
@Deprecated
static final String JPA_VALIDATION_MODE
```
    Deprecated.
    Use JAKARTA_VALIDATION_MODE instead
    
    Used to indicate what form of automatic validation is in effect as per rules defined in JPA 2 section 3.6.1.1.
    See JPA 2 sections 9.4.3 and 8.2.1.8
    
    See Also:
    
    ValidationMode, Constant Field Values
  - JPA_VALIDATION_FACTORY
```
@Deprecated
static final String JPA_VALIDATION_FACTORY
```
    Deprecated.
    Use JAKARTA_VALIDATION_FACTORY instead
    
    Used to pass along any discovered validator factory.
    
    See Also:
    
    Constant Field Values
  - JPA_PERSIST_VALIDATION_GROUP
```
@Deprecated
static final String JPA_PERSIST_VALIDATION_GROUP
```
    Deprecated.
    Use JAKARTA_PERSIST_VALIDATION_GROUP instead
    
    Used to coordinate with bean validators.
    See JPA 2 section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JPA_UPDATE_VALIDATION_GROUP
```
@Deprecated
static final String JPA_UPDATE_VALIDATION_GROUP
```
    Deprecated.
    Use JAKARTA_UPDATE_VALIDATION_GROUP instead
    
    Used to coordinate with bean validators.
    See JPA 2 section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JPA_REMOVE_VALIDATION_GROUP
```
@Deprecated
static final String JPA_REMOVE_VALIDATION_GROUP
```
    Deprecated.
    Use JAKARTA_REMOVE_VALIDATION_GROUP instead
    
    Used to coordinate with bean validators.
    See JPA 2 section 8.2.1.9
    
    See Also:
    
    Constant Field Values
  - JPA_LOCK_SCOPE
```
@Deprecated
static final String JPA_LOCK_SCOPE
```
    Deprecated.
    Use JAKARTA_LOCK_SCOPE instead
    
    Used to request (hint) a pessimistic lock scope.
    See JPA 2 sections 8.2.1.9 and 3.4.4.3
    
    See Also:
    
    Constant Field Values
  - JPA_LOCK_TIMEOUT
```
@Deprecated
static final String JPA_LOCK_TIMEOUT
```
    Deprecated.
    Use JAKARTA_LOCK_TIMEOUT instead
    
    Used to request (hint) a pessimistic lock timeout (in milliseconds).
    See JPA 2 sections 8.2.1.9 and 3.4.4.3
    
    See Also:
    
    Constant Field Values
  - CDI_BEAN_MANAGER
```
@Deprecated
static final String CDI_BEAN_MANAGER
```
    Deprecated.
    Used to pass a CDI BeanManager to Hibernate.
    According to the JPA specification, the BeanManager should be passed at boot time and be ready for immediate use at that time. But not all environments can do this (WildFly, for example). To accommodate such environments, Hibernate provides two options:
    
    A proprietary CDI extension SPI (which has been proposed to the CDI spec group as a standard option) which can be used to provide delayed BeanManager access: to use this solution, the reference passed as the BeanManager during bootstrap should be typed as ExtendedBeanManager.
    Delayed access to the BeanManager reference: here, Hibernate will not access the reference passed as the BeanManager during bootstrap until it is first needed. Note, however, that this has the effect of delaying the detection of any deployment problems until after bootstrapping.
    This setting is used to configure access to the BeanManager, either directly, or via ExtendedBeanManager.
    See Also:
    
    Constant Field Values
  - FLUSH_MODE
```
static final String FLUSH_MODE
```
    Used to determine flush mode.
    
    See Also:
    
    HibernateHints.HINT_FLUSH_MODE, Constant Field Values
  - CFG_XML_FILE
```
static final String CFG_XML_FILE
```
    See Also:
    
    Constant Field Values
  - ORM_XML_FILES
```
static final String ORM_XML_FILES
```
    See Also:
    
    Constant Field Values
  - HBM_XML_FILES
```
static final String HBM_XML_FILES
```
    See Also:
    
    Constant Field Values
  - LOADED_CLASSES
```
static final String LOADED_CLASSES
```
    See Also:
    
    Constant Field Values
  - EVENT_LISTENER_PREFIX
```
static final String EVENT_LISTENER_PREFIX
```
    Event listener configuration properties follow the pattern hibernate.event.listener.eventType packageName.ClassName1, packageName.ClassName2
    
    See Also:
    
    Constant Field Values
  - CLASS_CACHE_PREFIX
```
static final String CLASS_CACHE_PREFIX
```
    Entity cache configuration properties follow the pattern hibernate.classcache.packagename.ClassName usage[, region] where usage is the cache strategy used and region the cache region name
    
    See Also:
    
    Constant Field Values
  - COLLECTION_CACHE_PREFIX
```
static final String COLLECTION_CACHE_PREFIX
```
    Collection cache configuration properties follow the pattern hibernate.collectioncache.packagename.ClassName.role usage[, region] where usage is the cache strategy used and region the cache region name
    
    See Also:
    
    Constant Field Values
  - ENHANCER_ENABLE_DIRTY_TRACKING
```
static final String ENHANCER_ENABLE_DIRTY_TRACKING
```
    Enable dirty tracking feature in runtime bytecode enhancement
    
    See Also:
    
    Constant Field Values
  - ENHANCER_ENABLE_LAZY_INITIALIZATION
```
static final String ENHANCER_ENABLE_LAZY_INITIALIZATION
```
    Enable lazy loading feature in runtime bytecode enhancement
    
    See Also:
    
    Constant Field Values
  - ENHANCER_ENABLE_ASSOCIATION_MANAGEMENT
```
static final String ENHANCER_ENABLE_ASSOCIATION_MANAGEMENT
```
    Enable association management feature in runtime bytecode enhancement
    
    See Also:
    
    Constant Field Values
  - PERSISTENCE_UNIT_NAME
```
static final String PERSISTENCE_UNIT_NAME
```
    Specifies the name of the persistence unit.
    
    See Also:
    
    Constant Field Values
  - SESSION_FACTORY_OBSERVER
```
static final String SESSION_FACTORY_OBSERVER
```
    Specifies a class which implements SessionFactoryObserver and has a constructor with no parameters.
    
    See Also:
    
    Constant Field Values
  - IDENTIFIER_GENERATOR_STRATEGY_PROVIDER
```
@Deprecated(since="6.0")
static final String IDENTIFIER_GENERATOR_STRATEGY_PROVIDER
```
    Deprecated.
    use GenerationTypeStrategyRegistration instead
    
    Specifies a class which implements IdentifierGeneratorStrategyProvider, and has a constructor with no parameters.
    
    See Also:
    
    Constant Field Values
  - DISCARD_PC_ON_CLOSE
```
static final String DISCARD_PC_ON_CLOSE
```
    When enabled, specifies that the persistent context should be discarded when either SharedSessionContract.close() or EntityManager.close() is called.
    By default, the persistent context is not discarded, as per the JPA specification.
    
    See Also:
    
    Constant Field Values

Interface AvailableSettings

Field Summary

Field Detail

JAKARTA_PERSISTENCE_PROVIDER

JAKARTA_TRANSACTION_TYPE

JAKARTA_JTA_DATASOURCE

JAKARTA_NON_JTA_DATASOURCE

JAKARTA_JDBC_DRIVER

JAKARTA_JDBC_URL

JAKARTA_JDBC_USER

JAKARTA_JDBC_PASSWORD

JAKARTA_SHARED_CACHE_MODE

JAKARTA_SHARED_CACHE_RETRIEVE_MODE

JAKARTA_SHARED_CACHE_STORE_MODE

JAKARTA_VALIDATION_MODE

JAKARTA_VALIDATION_FACTORY

JAKARTA_PERSIST_VALIDATION_GROUP

JAKARTA_UPDATE_VALIDATION_GROUP

JAKARTA_REMOVE_VALIDATION_GROUP

JAKARTA_LOCK_SCOPE

JAKARTA_LOCK_TIMEOUT

JAKARTA_CDI_BEAN_MANAGER

CLASSLOADERS

TC_CLASSLOADER

JPA_METAMODEL_POPULATION

STATIC_METAMODEL_POPULATION

CONNECTION_PROVIDER

DRIVER

URL

USER

PASS

ISOLATION

AUTOCOMMIT

POOL_SIZE

DATASOURCE

CONNECTION_PROVIDER_DISABLES_AUTOCOMMIT

CONNECTION_PREFIX

JNDI_CLASS

JNDI_URL

JNDI_PREFIX

DIALECT

DIALECT_RESOLVERS

DIALECT_DB_NAME

DIALECT_DB_VERSION

DIALECT_DB_MAJOR_VERSION

DIALECT_DB_MINOR_VERSION

STORAGE_ENGINE

SCHEMA_MANAGEMENT_TOOL

TRANSACTION_COORDINATOR_STRATEGY

JTA_PLATFORM

PREFER_USER_TRANSACTION

JTA_PLATFORM_RESOLVER

JTA_CACHE_TM

JTA_CACHE_UT

DEFAULT_CATALOG

DEFAULT_SCHEMA

DEFAULT_CACHE_CONCURRENCY_STRATEGY

FORCE_DISCRIMINATOR_IN_SELECTS_BY_DEFAULT

IMPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS

IGNORE_EXPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS

USE_NATIONALIZED_CHARACTER_DATA

SCANNER

SCANNER_ARCHIVE_INTERPRETER

SCANNER_DISCOVERY

IMPLICIT_NAMING_STRATEGY

PHYSICAL_NAMING_STRATEGY

ARTIFACT_PROCESSING_ORDER

KEYWORD_AUTO_QUOTING_ENABLED

XML_MAPPING_ENABLED

DEFAULT_LIST_SEMANTICS

SESSION_FACTORY_NAME

SESSION_FACTORY_NAME_IS_JNDI

SHOW_SQL

FORMAT_SQL

HIGHLIGHT_SQL

USE_SQL_COMMENTS

MAX_FETCH_DEPTH

DEFAULT_BATCH_FETCH_SIZE

USE_SCROLLABLE_RESULTSET

USE_GET_GENERATED_KEYS