java.lang.Object
- org.hibernate.boot.spi.AbstractDelegatingSessionFactoryBuilder<T>

类型参数:

T - The type of a specific sub-class; Allows sub-classes to narrow down the return-type of the contract methods to a specialization of SessionFactoryBuilder

所有已实现的接口:

SessionFactoryBuilder

直接已知子类:

AbstractDelegatingSessionFactoryBuilderImplementor
```
public abstract class AbstractDelegatingSessionFactoryBuilder<T extends SessionFactoryBuilder>
extends Object
implements SessionFactoryBuilder
```
Convenience base class for custom implementors of SessionFactoryBuilder, using delegation

作者:

Steve Ebersole, Gunnar Morling, Guillaume Smet

构造器概要

构造器
构造器说明

AbstractDelegatingSessionFactoryBuilder(SessionFactoryBuilder delegate)

方法概要

所有方法实例方法抽象方法具体方法
修饰符和类型	方法	说明
`T`	`addEntityNameResolver(EntityNameResolver... entityNameResolvers)`	Specifies one or more entity name resolvers to be applied to the SessionFactory (see the `EntityNameResolver` contract for more information..
`T`	`addSessionFactoryObservers(SessionFactoryObserver... observers)`	Specifies one or more observers to be applied to the SessionFactory.
`T`	`allowOutOfTransactionUpdateOperations(boolean allow)`
`T`	`applyAutoClosing(boolean enabled)`	Applies whether Sessions should be automatically closed at the end of the transaction.
`T`	`applyAutoFlushing(boolean enabled)`	Applies whether Sessions should be automatically flushed at the end of the transaction.
`T`	`applyAutomaticEvictionOfCollectionCaches(boolean enabled)`	When using bi-directional many-to-one associations and caching the one-to-many side it is expected that both sides of the association are managed (actually that is true of all bi-directional associations).
`T`	`applyBatchFetchStyle(BatchFetchStyle style)`	What style of batching should be used?
`T`	`applyBeanManager(Object beanManager)`	Apply a CDI BeanManager to the SessionFactory being built.
`T`	`applyCacheRegionPrefix(String prefix)`	Apply a prefix to prepended to all cache region names for this SessionFactory.
`T`	`applyConnectionHandlingMode(PhysicalConnectionHandlingMode connectionHandlingMode)`	Apply the specified handling mode for JDBC connections
`SessionFactoryBuilder`	`applyConnectionProviderDisablesAutoCommit(boolean providerDisablesAutoCommit)`
`T`	`applyConnectionReleaseMode(ConnectionReleaseMode connectionReleaseMode)`	Apply a ConnectionReleaseMode.
`T`	`applyCurrentTenantIdentifierResolver(CurrentTenantIdentifierResolver resolver)`	Specifies a strategy for resolving the notion of a "current" tenant-identifier when using multi-tenancy together with current sessions
`T`	`applyCustomEntityDirtinessStrategy(CustomEntityDirtinessStrategy strategy)`	Specifies a custom entity dirtiness strategy to be applied to the SessionFactory.
`T`	`applyDefaultBatchFetchSize(int size)`	Allows specifying a default batch-fetch size for all entities and collections which do not otherwise specify a batch-fetch size.
`T`	`applyDefaultEntityMode(EntityMode entityMode)`	Applies the given entity mode as the default for the SessionFactory.
`T`	`applyDefaultNullPrecedence(NullPrecedence nullPrecedence)`	Apply a null precedence (NULLS FIRST, NULLS LAST) to be applied order-by clauses rendered into SQL queries.
`SessionFactoryBuilder`	`applyDelayedEntityLoaderCreations(boolean delay)`	Should entity Loaders be generated immediately?
`T`	`applyDirectReferenceCaching(boolean enabled)`	Generally, Hibernate will extract the information from an entity and put that extracted information into the second-level cache.
`T`	`applyEntityNotFoundDelegate(EntityNotFoundDelegate entityNotFoundDelegate)`	Names the `EntityNotFoundDelegate` to be applied to the SessionFactory.
`T`	`applyEntityTuplizer(EntityMode entityMode, Class<? extends EntityTuplizer> tuplizerClass)`	Register the default `EntityTuplizer` to be applied to the SessionFactory.
`T`	`applyEntityTuplizerFactory(EntityTuplizerFactory entityTuplizerFactory)`	Specify the EntityTuplizerFactory to use.
`T`	`applyGetGeneratedKeysSupport(boolean enabled)`	Should JDBC `Statement.getGeneratedKeys()` feature be used for retrieval of insert-generated ids?
`T`	`applyIdentifierRollbackSupport(boolean enabled)`	Should generated identifiers be "unset" on entities during a rollback?
`T`	`applyInterceptor(Interceptor interceptor)`	Names an interceptor to be applied to the SessionFactory, which in turn means it will be used by all Sessions unless one is explicitly specified in `SessionBuilder.interceptor(org.hibernate.Interceptor)`
`T`	`applyJdbcBatchingForVersionedEntities(boolean enabled)`	This setting controls whether versioned entities will be included in JDBC batching.
`T`	`applyJdbcBatchSize(int size)`	Specifies the maximum number of statements to batch together in a JDBC batch for insert, update and delete operations.
`T`	`applyJdbcFetchSize(int size)`	Apply a fetch size to the JDBC driver for fetching results.
`T`	`applyJtaTrackingByThread(boolean enabled)`	If using the built-in Hibernate JTA-based TransactionCoordinator/Builder, should it track JTA transactions by thread in an attempt to detect timeouts?
`T`	`applyLazyInitializationOutsideTransaction(boolean enabled)`	Should the application be allowed to initialize uninitialized lazy state outside the bounds of a transaction?
`T`	`applyMaximumFetchDepth(int depth)`	Apply a limit to the depth Hibernate will use for outer joins.
`T`	`applyMinimalPutsForCaching(boolean enabled)`	By default, Hibernate will always just push data into the cache without first checking if that data already exists.
`T`	`applyMultiTableBulkIdStrategy(MultiTableBulkIdStrategy strategy)`	How should updates and deletes that span multiple tables be handled?
`T`	`applyMultiTenancyStrategy(MultiTenancyStrategy strategy)`	Apply the form of multi-tenancy used by the application
`T`	`applyName(String sessionFactoryName)`	Applies a SessionFactory name.
`T`	`applyNameAsJndiName(boolean isJndiName)`	Applies a SessionFactory name.
`T`	`applyNamedQueryCheckingOnStartup(boolean enabled)`	Should named queries be checked on startup?
`T`	`applyNullabilityChecking(boolean enabled)`	Should attributes using columns marked as not-null be checked (by Hibernate) for nullness?
`T`	`applyOrderingOfInserts(boolean enabled)`	Apply whether ordering of inserts should be enabled.
`T`	`applyOrderingOfUpdates(boolean enabled)`	Apply whether ordering of updates should be enabled.
`T`	`applyPreferUserTransactions(boolean preferUserTransactions)`	If using the built-in Hibernate JTA-based TransactionCoordinator/Builder, should it prefer to use `UserTransaction` over `Transaction`?
`T`	`applyQueryCacheSupport(boolean enabled)`	Should second level query caching support be enabled?
`T`	`applyQuerySubstitutions(Map substitutions)`	Apply query substitutions to use in HQL queries.
`T`	`applyResultSetsWrapping(boolean enabled)`	Hibernate currently accesses results from the JDBC ResultSet by name.
`T`	`applyScrollableResultsSupport(boolean enabled)`	Should scrollable results be supported in queries?
`T`	`applySecondLevelCacheSupport(boolean enabled)`	Should second level caching support be enabled?
`T`	`applySqlComments(boolean enabled)`	Should Hibernate apply comments to SQL it generates?
`T`	`applySqlFunction(String registrationName, SQLFunction sqlFunction)`	Apply a SQLFunction to the underlying `SQLFunctionRegistry`.
`T`	`applyStatelessInterceptor(Class<? extends Interceptor> statelessInterceptorClass)`	Names an interceptor Class to be applied to the SessionFactory, which in turn means it will be used by all Sessions unless one is explicitly specified in `SessionBuilder.interceptor(org.hibernate.Interceptor)`
`T`	`applyStatelessInterceptor(Supplier<? extends Interceptor> statelessInterceptorSupplier)`	Names a `Supplier` instance which is used to retrieve the interceptor to be applied to the SessionFactory, which in turn means it will be used by all Sessions unless one is explicitly specified in `SessionBuilder.interceptor(org.hibernate.Interceptor)`
`T`	`applyStatementInspector(StatementInspector statementInspector)`	Names a StatementInspector to be applied to the SessionFactory, which in turn means it will be used by all Sessions unless one is explicitly specified in `SessionBuilder.statementInspector(org.hibernate.resource.jdbc.spi.StatementInspector)`
`T`	`applyStatisticsSupport(boolean enabled)`	Applies whether statistics gathering is enabled.
`T`	`applyStrictJpaQueryLanguageCompliance(boolean enabled)`	Should we strictly adhere to JPA Query Language (JPQL) syntax, or more broadly support all of Hibernate's superset (HQL)?
`T`	`applyStructuredCacheEntries(boolean enabled)`	By default, Hibernate stores data in the cache in its own optimized format.
`T`	`applyTempTableDdlTransactionHandling(TempTableDdlTransactionHandling handling)`
`SessionFactoryBuilder`	`applyTimestampsCacheFactory(TimestampsCacheFactory factory)`	Specifies a QueryCacheFactory to use for building query cache handlers.
`T`	`applyValidatorFactory(Object validatorFactory)`	Apply a Bean Validation ValidatorFactory to the SessionFactory being built.
`SessionFactory`	`build()`	After all options have been set, build the SessionFactory.
`protected SessionFactoryBuilder`	`delegate()`
`SessionFactoryBuilder`	`enableJpaClosedCompliance(boolean enabled)`
`SessionFactoryBuilder`	`enableJpaListCompliance(boolean enabled)`
`SessionFactoryBuilder`	`enableJpaQueryCompliance(boolean enabled)`
`SessionFactoryBuilder`	`enableJpaTransactionCompliance(boolean enabled)`
`T`	`enableReleaseResourcesOnCloseEnabled(boolean enable)`	Should resources held by `EntityManager` instance be released immediately on close?
`protected abstract T`	`getThis()`	Returns a specific implementation.
`<S extends SessionFactoryBuilder> S`	`unwrap(Class<S> type)`	Allows unwrapping this builder as another, more specific type.

从类继承的方法 java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- 构造器详细资料
  - AbstractDelegatingSessionFactoryBuilder
```
public AbstractDelegatingSessionFactoryBuilder(SessionFactoryBuilder delegate)
```
- 方法详细资料
  - getThis
```
protected abstract T getThis()
```
    Returns a specific implementation. See the What is the "getThis trick?".
  - delegate
```
protected SessionFactoryBuilder delegate()
```
  - applyValidatorFactory
```
public T applyValidatorFactory(Object validatorFactory)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Apply a Bean Validation ValidatorFactory to the SessionFactory being built. NOTE : De-typed to avoid hard dependency on Bean Validation jar at runtime.
    
    指定者:
    
    applyValidatorFactory 在接口中 SessionFactoryBuilder
    
    参数:
    
    validatorFactory - The Bean Validation ValidatorFactory to use
    
    返回:
    
    this, for method chaining
  - applyBeanManager
```
public T applyBeanManager(Object beanManager)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Apply a CDI BeanManager to the SessionFactory being built. NOTE : De-typed to avoid hard dependency on CDI jar at runtime.
    
    指定者:
    
    applyBeanManager 在接口中 SessionFactoryBuilder
    
    参数:
    
    beanManager - The CDI BeanManager to use
    
    返回:
    
    this, for method chaining
  - applyName
```
public T applyName(String sessionFactoryName)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Applies a SessionFactory name.
    
    指定者:
    
    applyName 在接口中 SessionFactoryBuilder
    
    参数:
    
    sessionFactoryName - The name to use for the SessionFactory being built
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.SESSION_FACTORY_NAME
  - applyNameAsJndiName
```
public T applyNameAsJndiName(boolean isJndiName)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Applies a SessionFactory name.
    
    指定者:
    
    applyNameAsJndiName 在接口中 SessionFactoryBuilder
    
    参数:
    
    isJndiName - true indicates that the name specified in SessionFactoryBuilder.applyName(java.lang.String) will be used for binding the SessionFactory into JNDI.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.SESSION_FACTORY_NAME_IS_JNDI
  - applyAutoClosing
```
public T applyAutoClosing(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Applies whether Sessions should be automatically closed at the end of the transaction.
    
    指定者:
    
    applyAutoClosing 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates they should be auto-closed; false indicates not.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.AUTO_CLOSE_SESSION
  - applyAutoFlushing
```
public T applyAutoFlushing(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Applies whether Sessions should be automatically flushed at the end of the transaction.
    
    指定者:
    
    applyAutoFlushing 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates they should be auto-flushed; false indicates not.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.FLUSH_BEFORE_COMPLETION
  - applyStatisticsSupport
```
public T applyStatisticsSupport(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Applies whether statistics gathering is enabled.
    
    指定者:
    
    applyStatisticsSupport 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates that statistics gathering should be enabled; false indicates not.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.GENERATE_STATISTICS
  - applyInterceptor
```
public T applyInterceptor(Interceptor interceptor)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Names an interceptor to be applied to the SessionFactory, which in turn means it will be used by all Sessions unless one is explicitly specified in SessionBuilder.interceptor(org.hibernate.Interceptor)
    
    指定者:
    
    applyInterceptor 在接口中 SessionFactoryBuilder
    
    参数:
    
    interceptor - The interceptor
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.INTERCEPTOR
  - applyStatementInspector
```
public T applyStatementInspector(StatementInspector statementInspector)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Names a StatementInspector to be applied to the SessionFactory, which in turn means it will be used by all Sessions unless one is explicitly specified in SessionBuilder.statementInspector(org.hibernate.resource.jdbc.spi.StatementInspector)
    
    指定者:
    
    applyStatementInspector 在接口中 SessionFactoryBuilder
    
    参数:
    
    statementInspector - The StatementInspector
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.STATEMENT_INSPECTOR
  - addSessionFactoryObservers
```
public T addSessionFactoryObservers(SessionFactoryObserver... observers)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Specifies one or more observers to be applied to the SessionFactory. Can be called multiple times to add additional observers.
    
    指定者:
    
    addSessionFactoryObservers 在接口中 SessionFactoryBuilder
    
    参数:
    
    observers - The observers to add
    
    返回:
    
    this, for method chaining
  - applyCustomEntityDirtinessStrategy
```
public T applyCustomEntityDirtinessStrategy(CustomEntityDirtinessStrategy strategy)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Specifies a custom entity dirtiness strategy to be applied to the SessionFactory. See the contract of CustomEntityDirtinessStrategy for details.
    
    指定者:
    
    applyCustomEntityDirtinessStrategy 在接口中 SessionFactoryBuilder
    
    参数:
    
    strategy - The custom strategy to be used.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.CUSTOM_ENTITY_DIRTINESS_STRATEGY
  - addEntityNameResolver
```
public T addEntityNameResolver(EntityNameResolver... entityNameResolvers)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Specifies one or more entity name resolvers to be applied to the SessionFactory (see the EntityNameResolver contract for more information.. Can be called multiple times to add additional resolvers..
    
    指定者:
    
    addEntityNameResolver 在接口中 SessionFactoryBuilder
    
    参数:
    
    entityNameResolvers - The entityNameResolvers to add
    
    返回:
    
    this, for method chaining
  - applyEntityNotFoundDelegate
```
public T applyEntityNotFoundDelegate(EntityNotFoundDelegate entityNotFoundDelegate)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Names the EntityNotFoundDelegate to be applied to the SessionFactory. EntityNotFoundDelegate is a strategy that accounts for different exceptions thrown between Hibernate and JPA when an entity cannot be found.
    
    指定者:
    
    applyEntityNotFoundDelegate 在接口中 SessionFactoryBuilder
    
    参数:
    
    entityNotFoundDelegate - The delegate/strategy to use.
    
    返回:
    
    this, for method chaining
  - applyIdentifierRollbackSupport
```
public T applyIdentifierRollbackSupport(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Should generated identifiers be "unset" on entities during a rollback?
    
    指定者:
    
    applyIdentifierRollbackSupport 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates identifiers should be unset; false indicates not.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.USE_IDENTIFIER_ROLLBACK
  - applyDefaultEntityMode
```
public T applyDefaultEntityMode(EntityMode entityMode)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Applies the given entity mode as the default for the SessionFactory.
    
    指定者:
    
    applyDefaultEntityMode 在接口中 SessionFactoryBuilder
    
    参数:
    
    entityMode - The default entity mode to use.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.DEFAULT_ENTITY_MODE
  - applyNullabilityChecking
```
public T applyNullabilityChecking(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Should attributes using columns marked as not-null be checked (by Hibernate) for nullness?
    
    指定者:
    
    applyNullabilityChecking 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates that Hibernate should perform nullness checking; false indicates it should not.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.CHECK_NULLABILITY
  - applyLazyInitializationOutsideTransaction
```
public T applyLazyInitializationOutsideTransaction(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Should the application be allowed to initialize uninitialized lazy state outside the bounds of a transaction?
    
    指定者:
    
    applyLazyInitializationOutsideTransaction 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates initialization outside the transaction should be allowed; false indicates it should not.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.ENABLE_LAZY_LOAD_NO_TRANS
  - applyEntityTuplizerFactory
```
public T applyEntityTuplizerFactory(EntityTuplizerFactory entityTuplizerFactory)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Specify the EntityTuplizerFactory to use.
    
    指定者:
    
    applyEntityTuplizerFactory 在接口中 SessionFactoryBuilder
    
    参数:
    
    entityTuplizerFactory - The EntityTuplizerFactory to use.
    
    返回:
    
    this, for method chaining
  - applyEntityTuplizer
```
public T applyEntityTuplizer(EntityMode entityMode,
                             Class<? extends EntityTuplizer> tuplizerClass)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Register the default EntityTuplizer to be applied to the SessionFactory.
    
    指定者:
    
    applyEntityTuplizer 在接口中 SessionFactoryBuilder
    
    参数:
    
    entityMode - The entity mode that which this tuplizer will be applied.
    
    tuplizerClass - The custom tuplizer class.
    
    返回:
    
    this, for method chaining
  - applyMultiTableBulkIdStrategy
```
public T applyMultiTableBulkIdStrategy(MultiTableBulkIdStrategy strategy)
```
    从接口复制的说明: SessionFactoryBuilder
    
    How should updates and deletes that span multiple tables be handled?
    
    指定者:
    
    applyMultiTableBulkIdStrategy 在接口中 SessionFactoryBuilder
    
    参数:
    
    strategy - The strategy for handling multi-table updates and deletes.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.HQL_BULK_ID_STRATEGY
  - applyTempTableDdlTransactionHandling
```
public T applyTempTableDdlTransactionHandling(TempTableDdlTransactionHandling handling)
```
    指定者:
    
    applyTempTableDdlTransactionHandling 在接口中 SessionFactoryBuilder
  - applyBatchFetchStyle
```
public T applyBatchFetchStyle(BatchFetchStyle style)
```
    从接口复制的说明: SessionFactoryBuilder
    
    What style of batching should be used?
    
    指定者:
    
    applyBatchFetchStyle 在接口中 SessionFactoryBuilder
    
    参数:
    
    style - The style to use
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.BATCH_FETCH_STYLE
  - applyDelayedEntityLoaderCreations
```
public SessionFactoryBuilder applyDelayedEntityLoaderCreations(boolean delay)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Should entity Loaders be generated immediately? Or should the creation be delayed until first need?
    
    指定者:
    
    applyDelayedEntityLoaderCreations 在接口中 SessionFactoryBuilder
    
    另请参阅:
    
    AvailableSettings.DELAY_ENTITY_LOADER_CREATIONS
  - applyDefaultBatchFetchSize
```
public T applyDefaultBatchFetchSize(int size)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Allows specifying a default batch-fetch size for all entities and collections which do not otherwise specify a batch-fetch size.
    
    指定者:
    
    applyDefaultBatchFetchSize 在接口中 SessionFactoryBuilder
    
    参数:
    
    size - The size to use for batch fetching for entities/collections which do not specify an explicit batch fetch size.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.DEFAULT_BATCH_FETCH_SIZE
  - applyMaximumFetchDepth
```
public T applyMaximumFetchDepth(int depth)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Apply a limit to the depth Hibernate will use for outer joins. Note that this is different than an overall limit on the number of joins...
    
    指定者:
    
    applyMaximumFetchDepth 在接口中 SessionFactoryBuilder
    
    参数:
    
    depth - The depth for limiting joins.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.MAX_FETCH_DEPTH
  - applyDefaultNullPrecedence
```
public T applyDefaultNullPrecedence(NullPrecedence nullPrecedence)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Apply a null precedence (NULLS FIRST, NULLS LAST) to be applied order-by clauses rendered into SQL queries.
    
    指定者:
    
    applyDefaultNullPrecedence 在接口中 SessionFactoryBuilder
    
    参数:
    
    nullPrecedence - The default null precedence to use.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.DEFAULT_NULL_ORDERING
  - applyOrderingOfInserts
```
public T applyOrderingOfInserts(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Apply whether ordering of inserts should be enabled. This allows more efficient SQL generation via the use of batching for the inserts; the cost is that the determination of the ordering is far more inefficient than not ordering.
    
    指定者:
    
    applyOrderingOfInserts 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates that ordering should be enabled; false indicates not
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.ORDER_INSERTS
  - applyOrderingOfUpdates
```
public T applyOrderingOfUpdates(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Apply whether ordering of updates should be enabled. This allows more efficient SQL generation via the use of batching for the updates; the cost is that the determination of the ordering is far more inefficient than not ordering.
    
    指定者:
    
    applyOrderingOfUpdates 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates that ordering should be enabled; false indicates not
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.ORDER_UPDATES
  - applyMultiTenancyStrategy
```
public T applyMultiTenancyStrategy(MultiTenancyStrategy strategy)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Apply the form of multi-tenancy used by the application
    
    指定者:
    
    applyMultiTenancyStrategy 在接口中 SessionFactoryBuilder
    
    参数:
    
    strategy - The form of multi-tenancy in use.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.MULTI_TENANT
  - applyCurrentTenantIdentifierResolver
```
public T applyCurrentTenantIdentifierResolver(CurrentTenantIdentifierResolver resolver)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Specifies a strategy for resolving the notion of a "current" tenant-identifier when using multi-tenancy together with current sessions
    
    指定者:
    
    applyCurrentTenantIdentifierResolver 在接口中 SessionFactoryBuilder
    
    参数:
    
    resolver - The resolution strategy to use.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.MULTI_TENANT_IDENTIFIER_RESOLVER
  - applyJtaTrackingByThread
```
public T applyJtaTrackingByThread(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    If using the built-in Hibernate JTA-based TransactionCoordinator/Builder, should it track JTA transactions by thread in an attempt to detect timeouts?
    
    指定者:
    
    applyJtaTrackingByThread 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates we should track by thread; false indicates not
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.JTA_TRACK_BY_THREAD
  - applyPreferUserTransactions
```
public T applyPreferUserTransactions(boolean preferUserTransactions)
```
    从接口复制的说明: SessionFactoryBuilder
    
    If using the built-in Hibernate JTA-based TransactionCoordinator/Builder, should it prefer to use UserTransaction over Transaction?
    
    指定者:
    
    applyPreferUserTransactions 在接口中 SessionFactoryBuilder
    
    参数:
    
    preferUserTransactions - true indicates we should prefer UserTransaction; false indicates we should prefer Transaction
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.PREFER_USER_TRANSACTION
  - applyQuerySubstitutions
```
public T applyQuerySubstitutions(Map substitutions)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Apply query substitutions to use in HQL queries. Note, this is a legacy feature and almost always never needed anymore...
    
    指定者:
    
    applyQuerySubstitutions 在接口中 SessionFactoryBuilder
    
    参数:
    
    substitutions - The substitution map
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.QUERY_SUBSTITUTIONS
  - applyStrictJpaQueryLanguageCompliance
```
public T applyStrictJpaQueryLanguageCompliance(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Should we strictly adhere to JPA Query Language (JPQL) syntax, or more broadly support all of Hibernate's superset (HQL)?
    Setting this to true may cause valid HQL to throw an exception because it violates the JPQL subset.
    
    指定者:
    
    applyStrictJpaQueryLanguageCompliance 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates that we should strictly adhere to the JPQL subset; false indicates we should accept the broader HQL syntax.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.JPAQL_STRICT_COMPLIANCE
  - applyNamedQueryCheckingOnStartup
```
public T applyNamedQueryCheckingOnStartup(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Should named queries be checked on startup?
    
    指定者:
    
    applyNamedQueryCheckingOnStartup 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates that they should; false indicates they should not.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.QUERY_STARTUP_CHECKING
  - applySecondLevelCacheSupport
```
public T applySecondLevelCacheSupport(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Should second level caching support be enabled?
    
    指定者:
    
    applySecondLevelCacheSupport 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates we should enable the use of second level caching; false indicates we should disable the use of second level caching.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.USE_SECOND_LEVEL_CACHE
  - applyQueryCacheSupport
```
public T applyQueryCacheSupport(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Should second level query caching support be enabled?
    
    指定者:
    
    applyQueryCacheSupport 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates we should enable the use of second level query caching; false indicates we should disable the use of second level query caching.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.USE_QUERY_CACHE
  - applyTimestampsCacheFactory
```
public SessionFactoryBuilder applyTimestampsCacheFactory(TimestampsCacheFactory factory)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Specifies a QueryCacheFactory to use for building query cache handlers.
    
    指定者:
    
    applyTimestampsCacheFactory 在接口中 SessionFactoryBuilder
    
    参数:
    
    factory - The QueryCacheFactory to use
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.QUERY_CACHE_FACTORY
  - applyCacheRegionPrefix
```
public T applyCacheRegionPrefix(String prefix)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Apply a prefix to prepended to all cache region names for this SessionFactory.
    
    指定者:
    
    applyCacheRegionPrefix 在接口中 SessionFactoryBuilder
    
    参数:
    
    prefix - The prefix.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.CACHE_REGION_PREFIX
  - applyMinimalPutsForCaching
```
public T applyMinimalPutsForCaching(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    By default, Hibernate will always just push data into the cache without first checking if that data already exists. For some caches (mainly distributed caches) this can have a major adverse performance impact. For these caches, it is best to enable this "minimal puts" feature.
    Cache integrations also report whether "minimal puts" should be enabled by default. So its is very rare that users need to set this, generally speaking.
    
    指定者:
    
    applyMinimalPutsForCaching 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates Hibernate should first check whether data exists and only push to the cache if it does not already exist. false indicates to perform the default behavior.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.USE_MINIMAL_PUTS, RegionFactory.isMinimalPutsEnabledByDefault()
  - applyStructuredCacheEntries
```
public T applyStructuredCacheEntries(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    By default, Hibernate stores data in the cache in its own optimized format. However, that format is impossible to "read" if browsing the cache. The use of "structured" cache entries allows the cached data to be read.
    
    指定者:
    
    applyStructuredCacheEntries 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates that structured cache entries (human readable) should be used; false indicates that the native entry structure should be used.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.USE_STRUCTURED_CACHE
  - applyDirectReferenceCaching
```
public T applyDirectReferenceCaching(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Generally, Hibernate will extract the information from an entity and put that extracted information into the second-level cache. This is by far the safest way to second-level cache persistent data. However, there are some cases where it is safe to cache the entity instance directly. This setting controls whether that is used in those cases.
    
    指定者:
    
    applyDirectReferenceCaching 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates that applicable entities will be stored into the second-level cache directly by reference; false indicates that all entities will be stored via the extraction approach.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.USE_DIRECT_REFERENCE_CACHE_ENTRIES
  - applyAutomaticEvictionOfCollectionCaches
```
public T applyAutomaticEvictionOfCollectionCaches(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    When using bi-directional many-to-one associations and caching the one-to-many side it is expected that both sides of the association are managed (actually that is true of all bi-directional associations). However, in this case, if the user forgets to manage the one-to-many side stale data can be left in the second-level cache.
    Warning: enabling this will have a performance impact. Hence why it is disabled by default (for good citizens) and is an opt-in setting.
    
    指定者:
    
    applyAutomaticEvictionOfCollectionCaches 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates that these collection caches should be evicted automatically.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.AUTO_EVICT_COLLECTION_CACHE
  - applyJdbcBatchSize
```
public T applyJdbcBatchSize(int size)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Specifies the maximum number of statements to batch together in a JDBC batch for insert, update and delete operations. A non-zero number enables batching, but really only a number greater than zero will have any effect. If used, a number great than 5 is suggested.
    
    指定者:
    
    applyJdbcBatchSize 在接口中 SessionFactoryBuilder
    
    参数:
    
    size - The batch size to use.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.STATEMENT_BATCH_SIZE
  - applyJdbcBatchingForVersionedEntities
```
public T applyJdbcBatchingForVersionedEntities(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    This setting controls whether versioned entities will be included in JDBC batching. The reason being that some JDBC drivers have a problems returning "accurate" update counts from batch statements. This is setting is false by default.
    
    指定者:
    
    applyJdbcBatchingForVersionedEntities 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - The batch size to use.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.BATCH_VERSIONED_DATA
  - applyScrollableResultsSupport
```
public T applyScrollableResultsSupport(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Should scrollable results be supported in queries? We ask the JDBC driver whether it supports scrollable result sets as the default for this setting, but some drivers do not accurately report this via DatabaseMetaData. Also, needed if user is supplying connections (and so no Connection is available when we bootstrap).
    
    指定者:
    
    applyScrollableResultsSupport 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true to enable this support, false to disable it
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.USE_SCROLLABLE_RESULTSET
  - applyResultSetsWrapping
```
public T applyResultSetsWrapping(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Hibernate currently accesses results from the JDBC ResultSet by name. This is known to be VERY slow on some drivers, especially older Oracle drivers. This setting allows Hibernate to wrap the ResultSet of the JDBC driver to manage the name->position resolution itself.
    
    指定者:
    
    applyResultSetsWrapping 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates Hibernate should wrap result sets; false indicates it should not.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.WRAP_RESULT_SETS
  - applyGetGeneratedKeysSupport
```
public T applyGetGeneratedKeysSupport(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Should JDBC Statement.getGeneratedKeys() feature be used for retrieval of *insert-generated* ids?
    
    指定者:
    
    applyGetGeneratedKeysSupport 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates we should use JDBC getGeneratedKeys support; false indicates we should not.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.USE_GET_GENERATED_KEYS
  - applyJdbcFetchSize
```
public T applyJdbcFetchSize(int size)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Apply a fetch size to the JDBC driver for fetching results.
    
    指定者:
    
    applyJdbcFetchSize 在接口中 SessionFactoryBuilder
    
    参数:
    
    size - The fetch size to be passed to the driver.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.USE_GET_GENERATED_KEYS, Statement.setFetchSize(int)
  - applyConnectionReleaseMode
```
public T applyConnectionReleaseMode(ConnectionReleaseMode connectionReleaseMode)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Apply a ConnectionReleaseMode.
    
    指定者:
    
    applyConnectionReleaseMode 在接口中 SessionFactoryBuilder
    
    参数:
    
    connectionReleaseMode - The ConnectionReleaseMode to use.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.RELEASE_CONNECTIONS
  - applyConnectionProviderDisablesAutoCommit
```
public SessionFactoryBuilder applyConnectionProviderDisablesAutoCommit(boolean providerDisablesAutoCommit)
```
    指定者:
    
    applyConnectionProviderDisablesAutoCommit 在接口中 SessionFactoryBuilder
    
    另请参阅:
    
    AvailableSettings.CONNECTION_PROVIDER_DISABLES_AUTOCOMMIT
  - applySqlComments
```
public T applySqlComments(boolean enabled)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Should Hibernate apply comments to SQL it generates?
    
    指定者:
    
    applySqlComments 在接口中 SessionFactoryBuilder
    
    参数:
    
    enabled - true indicates comments should be applied; false indicates not.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.USE_SQL_COMMENTS
  - applySqlFunction
```
public T applySqlFunction(String registrationName,
                          SQLFunction sqlFunction)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Apply a SQLFunction to the underlying SQLFunctionRegistry.
    TODO : Ultimately I would like this to move to MetadataBuilder in conjunction with allowing mappings to reference SQLFunctions. today mappings can only name SQL functions directly, not through the SQLFunctionRegistry indirection
    
    指定者:
    
    applySqlFunction 在接口中 SessionFactoryBuilder
    
    参数:
    
    registrationName - The name to register it under.
    
    sqlFunction - The SQLFunction impl
    
    返回:
    
    this, for method chaining
  - allowOutOfTransactionUpdateOperations
```
public T allowOutOfTransactionUpdateOperations(boolean allow)
```
    指定者:
    
    allowOutOfTransactionUpdateOperations 在接口中 SessionFactoryBuilder
  - enableReleaseResourcesOnCloseEnabled
```
public T enableReleaseResourcesOnCloseEnabled(boolean enable)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Should resources held by EntityManager instance be released immediately on close?
    The other option is to release them as part of an after-transaction callback.
    
    指定者:
    
    enableReleaseResourcesOnCloseEnabled 在接口中 SessionFactoryBuilder
  - enableJpaQueryCompliance
```
public SessionFactoryBuilder enableJpaQueryCompliance(boolean enabled)
```
    指定者:
    
    enableJpaQueryCompliance 在接口中 SessionFactoryBuilder
    
    另请参阅:
    
    JpaCompliance.isJpaQueryComplianceEnabled()
  - enableJpaTransactionCompliance
```
public SessionFactoryBuilder enableJpaTransactionCompliance(boolean enabled)
```
    指定者:
    
    enableJpaTransactionCompliance 在接口中 SessionFactoryBuilder
    
    另请参阅:
    
    JpaCompliance.isJpaTransactionComplianceEnabled()
  - enableJpaListCompliance
```
public SessionFactoryBuilder enableJpaListCompliance(boolean enabled)
```
    指定者:
    
    enableJpaListCompliance 在接口中 SessionFactoryBuilder
    
    另请参阅:
    
    JpaCompliance.isJpaListComplianceEnabled()
  - enableJpaClosedCompliance
```
public SessionFactoryBuilder enableJpaClosedCompliance(boolean enabled)
```
    指定者:
    
    enableJpaClosedCompliance 在接口中 SessionFactoryBuilder
    
    另请参阅:
    
    JpaCompliance.isJpaClosedComplianceEnabled()
  - unwrap
```
public <S extends SessionFactoryBuilder> S unwrap(Class<S> type)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Allows unwrapping this builder as another, more specific type.
    
    指定者:
    
    unwrap 在接口中 SessionFactoryBuilder
    
    返回:
    
    The unwrapped builder.
  - applyStatelessInterceptor
```
public T applyStatelessInterceptor(Supplier<? extends Interceptor> statelessInterceptorSupplier)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Names a Supplier instance which is used to retrieve the interceptor to be applied to the SessionFactory, which in turn means it will be used by all Sessions unless one is explicitly specified in SessionBuilder.interceptor(org.hibernate.Interceptor)
    
    指定者:
    
    applyStatelessInterceptor 在接口中 SessionFactoryBuilder
    
    参数:
    
    statelessInterceptorSupplier - Supplier instance which is used to retrieve the interceptor
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.SESSION_SCOPED_INTERCEPTOR
  - applyStatelessInterceptor
```
public T applyStatelessInterceptor(Class<? extends Interceptor> statelessInterceptorClass)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Names an interceptor Class to be applied to the SessionFactory, which in turn means it will be used by all Sessions unless one is explicitly specified in SessionBuilder.interceptor(org.hibernate.Interceptor)
    
    指定者:
    
    applyStatelessInterceptor 在接口中 SessionFactoryBuilder
    
    参数:
    
    statelessInterceptorClass - The interceptor class
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.SESSION_SCOPED_INTERCEPTOR
  - applyConnectionHandlingMode
```
public T applyConnectionHandlingMode(PhysicalConnectionHandlingMode connectionHandlingMode)
```
    从接口复制的说明: SessionFactoryBuilder
    
    Apply the specified handling mode for JDBC connections
    
    指定者:
    
    applyConnectionHandlingMode 在接口中 SessionFactoryBuilder
    
    参数:
    
    connectionHandlingMode - The handling mode to apply
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.ACQUIRE_CONNECTIONS, AvailableSettings.RELEASE_CONNECTIONS, ConnectionAcquisitionMode, ConnectionReleaseMode
  - build
```
public SessionFactory build()
```
    从接口复制的说明: SessionFactoryBuilder
    
    After all options have been set, build the SessionFactory.
    
    指定者:
    
    build 在接口中 SessionFactoryBuilder
    
    返回:
    
    The built SessionFactory.

类 AbstractDelegatingSessionFactoryBuilder<T extends SessionFactoryBuilder>

构造器概要

方法概要

从类继承的方法 java.lang.Object

构造器详细资料

AbstractDelegatingSessionFactoryBuilder

方法详细资料

getThis

delegate

applyValidatorFactory

applyBeanManager

applyName

applyNameAsJndiName

applyAutoClosing

applyAutoFlushing

applyStatisticsSupport

applyInterceptor

applyStatementInspector

addSessionFactoryObservers

applyCustomEntityDirtinessStrategy

addEntityNameResolver

applyEntityNotFoundDelegate

applyIdentifierRollbackSupport

applyDefaultEntityMode

applyNullabilityChecking

applyLazyInitializationOutsideTransaction

applyEntityTuplizerFactory

applyEntityTuplizer

applyMultiTableBulkIdStrategy

applyTempTableDdlTransactionHandling

applyBatchFetchStyle

applyDelayedEntityLoaderCreations

applyDefaultBatchFetchSize

applyMaximumFetchDepth

applyDefaultNullPrecedence

applyOrderingOfInserts

applyOrderingOfUpdates

applyMultiTenancyStrategy

applyCurrentTenantIdentifierResolver

applyJtaTrackingByThread

applyPreferUserTransactions

applyQuerySubstitutions

applyStrictJpaQueryLanguageCompliance

applyNamedQueryCheckingOnStartup

applySecondLevelCacheSupport

applyQueryCacheSupport

applyTimestampsCacheFactory

applyCacheRegionPrefix

applyMinimalPutsForCaching

applyStructuredCacheEntries

applyDirectReferenceCaching

applyAutomaticEvictionOfCollectionCaches

applyJdbcBatchSize

applyJdbcBatchingForVersionedEntities

applyScrollableResultsSupport

applyResultSetsWrapping

applyGetGeneratedKeysSupport

applyJdbcFetchSize

applyConnectionReleaseMode

applyConnectionProviderDisablesAutoCommit

applySqlComments

applySqlFunction

allowOutOfTransactionUpdateOperations

enableReleaseResourcesOnCloseEnabled

enableJpaQueryCompliance

enableJpaTransactionCompliance

enableJpaListCompliance

enableJpaClosedCompliance

unwrap

applyStatelessInterceptor

applyStatelessInterceptor

applyConnectionHandlingMode

build