You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The configuration properties jakarta.persistence.database-product-name, jakarta.persistence.database-major-version, and jakarta.persistence.database-minor-version are currently defined as part of the container/provider contract.
But these properties are generally-useful as a way of configuring the persistence provider when access to JDBC metadata is not available at startup time (for example, in Quarkus, or in some cloud environments). And so Hibernate has never treated them as specific to container-based configuration.
We should promote these to the same status as other application-settable config properties, and add them to PersistenceConfiguration.
The text was updated successfully, but these errors were encountered:
Hibernate will use jakarta.persistence.database-xxxx for resolving dialect but EclipseLink will not, the specification only mention them for configuring the schema generation process, I think it should promoted too.
The configuration properties
jakarta.persistence.database-product-name
,jakarta.persistence.database-major-version
, andjakarta.persistence.database-minor-version
are currently defined as part of the container/provider contract.But these properties are generally-useful as a way of configuring the persistence provider when access to JDBC metadata is not available at startup time (for example, in Quarkus, or in some cloud environments). And so Hibernate has never treated them as specific to container-based configuration.
We should promote these to the same status as other application-settable config properties, and add them to
PersistenceConfiguration
.The text was updated successfully, but these errors were encountered: