类 MutableJpaComplianceImpl

    • 构造器详细资料

      • MutableJpaComplianceImpl

        public MutableJpaComplianceImpl​(Map configurationSettings,
                                        boolean jpaByDefault)
    • 方法详细资料

      • isJpaQueryComplianceEnabled

        public boolean isJpaQueryComplianceEnabled()
        从接口复制的说明: JpaCompliance
        Controls whether Hibernate's handling of JPA's Query (JPQL, Criteria and native-query) should strictly follow the JPA spec. This includes both in terms of parsing or translating a query as well as calls to the Query methods throwing spec defined exceptions where as Hibernate might not. Deviations result in an exception if enabled
        指定者:
        isJpaQueryComplianceEnabled 在接口中 JpaCompliance
        返回:
        true indicates to behave in the spec-defined way
      • isJpaTransactionComplianceEnabled

        public boolean isJpaTransactionComplianceEnabled()
        从接口复制的说明: JpaCompliance
        Indicates that Hibernate's Transaction should behave as defined by the spec for JPA's EntityTransaction since it extends the JPA one.
        指定者:
        isJpaTransactionComplianceEnabled 在接口中 JpaCompliance
        返回:
        true indicates to behave in the spec-defined way
      • isJpaListComplianceEnabled

        public boolean isJpaListComplianceEnabled()
        从接口复制的说明: JpaCompliance
        Controls how Hibernate interprets a mapped List without an "order columns" specified. Historically Hibernate defines this as a "bag", which is a concept JPA does not have. If enabled, Hibernate will recognize this condition as defining a PersistentList, otherwise Hibernate will treat is as a PersistentBag
        指定者:
        isJpaListComplianceEnabled 在接口中 JpaCompliance
        返回:
        true indicates to behave in the spec-defined way, interpreting the mapping as a "list", rather than a "bag"
      • isJpaClosedComplianceEnabled

        public boolean isJpaClosedComplianceEnabled()
        从接口复制的说明: JpaCompliance
        JPA defines specific exceptions on specific methods when called on EntityManager and EntityManagerFactory when those objects have been closed. This setting controls whether the spec defined behavior or Hibernate's behavior will be used. If enabled Hibernate will operate in the JPA specified way throwing exceptions when the spec says it should with regard to close checking
        指定者:
        isJpaClosedComplianceEnabled 在接口中 JpaCompliance
        返回:
        true indicates to behave in the spec-defined way
      • isJpaProxyComplianceEnabled

        public boolean isJpaProxyComplianceEnabled()
        从接口复制的说明: JpaCompliance
        JPA spec says that an EntityNotFoundException should be thrown when accessing an entity Proxy which does not have an associated table row in the database. Traditionally, Hibernate does not initialize an entity Proxy when accessing its identifier since we already know the identifier value, hence we can save a database roundtrip. If enabled Hibernate will initialize the entity Proxy even when accessing its identifier.
        指定者:
        isJpaProxyComplianceEnabled 在接口中 JpaCompliance
        返回:
        true indicates to behave in the spec-defined way
      • isJpaCacheComplianceEnabled

        public boolean isJpaCacheComplianceEnabled()
        从接口复制的说明: JpaCompliance
        Should Hibernate comply with all aspects of caching as defined by JPA? Or can it deviate to perform things it believes will be "better"?
        指定者:
        isJpaCacheComplianceEnabled 在接口中 JpaCompliance
        返回:
        true says to act the spec-defined way.
      • isGlobalGeneratorScopeEnabled

        public boolean isGlobalGeneratorScopeEnabled()
        从接口复制的说明: JpaCompliance
        Should the the scope of TableGenerator.name() and SequenceGenerator.name() be considered globally or locally defined?
        指定者:
        isGlobalGeneratorScopeEnabled 在接口中 JpaCompliance
        返回:
        true indicates the generator name scope is considered global.