Hibernate
/
hibernate-orm
mirror of https://github.com/hibernate/hibernate-orm
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

HHH-18080 Fix default version handling in dialects when not using JDBC metadata

This commit is contained in:
Steve Ebersole 2024-05-10 10:59:37 -05:00
parent 32d4f1596e
commit eb5a1ec714
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
migration-guide.adoc
View File

@ -95,11 +95,14 @@ unsupported for use by applications (as should have been obvious from the name).
This setting controls whether Hibernate should be allowed to access the JDBC `DatabaseMetaData` during bootstrapping.
With this setting enabled (the default), Hibernate will access the `DatabaseMetaData` to perform some internal
configuration based on the reported capabilities of the underlying database. Disabling this setting requires
explicit settings for this configuration. At a minimum this includes:
configuration based on the reported capabilities of the underlying database.
Disabling this setting requires explicit, additional settings for this configuration. At a minimum, this
includes `hibernate.dialect` or `jakarta.persistence.database-product-name` to indicate the type of database.
In such cases, Hibernate will assume the link:{userGuideBase}#compatibility-database[minimum supported version]
of the database (as reported by the link:{javadocsBase}/org/hibernate/dialect/Dialect.html#getMinimumSupportedVersion()[Dialect]).
Users may also configure `jakarta.persistence.database-product-version` to indicate a specific database version.
* `hibernate.dialect` or `jakarta.persistence.database-product-name` to indicate the type of database
* `jakarta.persistence.database-product-version` to indicate the database version
[[generic-generator]]
== Deprecation of `@GenericGenerator`