public Class MutableJpaComplianceImpl

Annotations

@SuppressWarnings:ConstantConditions

Implements org.hibernate.jpa.spi.MutableJpaCompliance.immutableCopy.

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isGlobalGeneratorScopeEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isGlobalGeneratorScopeEnabled.

Should the scope of jakarta.persistence.TableGenerator#name() and jakarta.persistence.SequenceGenerator#name() be considered globally or locally defined?

Returns:boolean

true if the generator name scope is considered global

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isJpaCacheComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isJpaCacheComplianceEnabled.

Should Hibernate comply with all aspects of caching as defined by JPA? Or can it deviate to perform things it believes will be "better"?

Returns:boolean

true indicates to behave in the spec-defined way

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isJpaClosedComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isJpaClosedComplianceEnabled.

JPA defines specific exceptions on specific methods when called on jakarta.persistence.EntityManager and jakarta.persistence.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

Returns:boolean

true indicates to behave in the spec-defined way

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isJpaListComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isJpaListComplianceEnabled.

Controls how Hibernate interprets a mapped java.util.List without no order column specified. Historically Hibernate treats this as a "bag", which is a concept JPA does not have.

• If enabled, Hibernate will recognize this case as a list.
• Otherwise, if disabled, Hibernate will treat it as a "bag".

Returns:boolean

true indicates to behave in the spec-defined way, interpreting the mapping as a "list", rather than a "bag"

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isJpaOrderByMappingComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isJpaOrderByMappingComplianceEnabled.

Should we strictly handle jakarta.persistence.OrderBy expressions?

JPA says the order-items can only be attribute references whereas Hibernate supports a wide range of items. With this enabled, Hibernate will throw a compliance error when a non-attribute-reference is used.

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isJpaProxyComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isJpaProxyComplianceEnabled.

JPA spec says that an jakarta.persistence.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 round trip.

If enabled Hibernate will initialize the entity proxy even when accessing its identifier.

Returns:boolean

true indicates to behave in the spec-defined way

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isJpaQueryComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isJpaQueryComplianceEnabled.

Controls whether Hibernate's handling of JPA's jakarta.persistence.Query (JPQL, Criteria and native-query) should strictly follow the JPA spec. This includes parsing and translating a query as JPQL instead of HQL, as well as whether calls to the jakarta.persistence.Query methods always throw the exceptions defined by the specification.

Deviations result in an exception, if enabled.

Returns:boolean

true indicates to behave in the spec-defined way

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isJpaTransactionComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isJpaTransactionComplianceEnabled.

Indicates that Hibernate's Transaction should behave as defined by the specification for JPA's jakarta.persistence.EntityTransaction since it extends it.

Returns:boolean

true indicates to behave in the spec-defined way

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isLoadByIdComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isLoadByIdComplianceEnabled.

JPA says that the id passed to jakarta.persistence.EntityManager#getReference and jakarta.persistence.EntityManager#find should be exactly the expected type, allowing no type coercion.

Historically, Hibernate behaved the same way. Since 6.0 however, Hibernate has the ability to coerce the passed type to the expected type. For example, an Integer may be widened to Long. Coercion is performed by calling org.hibernate.type.descriptor.java.JavaType#coerce.

This setting controls whether such coercion should be allowed.

Annotations

@Override

Implements org.hibernate.jpa.spi.MutableJpaCompliance.setCachingCompliance.

Annotations

@Override

Implements org.hibernate.jpa.spi.MutableJpaCompliance.setClosedCompliance.

Annotations

@Override

Implements org.hibernate.jpa.spi.MutableJpaCompliance.setGeneratorNameScopeCompliance.

Annotations

@Override

Implements org.hibernate.jpa.spi.MutableJpaCompliance.setListCompliance.

Annotations

@Override

Implements org.hibernate.jpa.spi.MutableJpaCompliance.setLoadByIdCompliance.

Annotations

@Override

Implements org.hibernate.jpa.spi.MutableJpaCompliance.setOrderByMappingCompliance.

Annotations

@Override

Implements org.hibernate.jpa.spi.MutableJpaCompliance.setProxyCompliance.

Annotations

@Override

Implements org.hibernate.jpa.spi.MutableJpaCompliance.setQueryCompliance.

Implements org.hibernate.jpa.spi.MutableJpaCompliance.setTransactionCompliance.

Annotations

@Override