This guide discusses migration to Hibernate ORM version 7.4. For migration from earlier versions, see any other pertinent migration guides as well.
See the website for the list of requirements for the 7.4 series.
See the website for the list of new features in the 7.4 series.
This section describes changes to contracts (classes, interfaces, methods, etc.) which are considered API.
This section describes changes to contracts (classes, interfaces, methods, etc.) which are considered SPI.
This section describes changes in behavior that applications should be aware of.
Previously, MySQLDialect defined a dialect-level default value of 2 for the
hibernate.max_fetch_depth configuration property.
As of Hibernate ORM 7.4, this dialect-specific default has been removed. MySQL now behaves consistently with other dialects and relies on Hibernate’s general defaults or explicit user configuration.
Applications that relied on the previous implicit default should explicitly set
hibernate.max_fetch_depth if required.
This section describes changes to DDL generated by the schema export tooling. Such changes typically do not impact programs using a relational schema managed externally to Hibernate.