initial migration guide
This commit is contained in:
parent
40d0c8580e
commit
fe25fee834
|
@ -1,7 +1,7 @@
|
|||
= 5.4 Migration Guide
|
||||
= 6.0 Migration Guide
|
||||
:toc:
|
||||
|
||||
This guide discusses migration from Hibernate ORM version 5.3 to version 5.4. For migration from
|
||||
This guide discusses migration from Hibernate ORM version 6.0. For migration from
|
||||
earlier versions, see any other pertinent migration guides as well.
|
||||
|
||||
== Background
|
||||
|
@ -9,33 +9,14 @@ earlier versions, see any other pertinent migration guides as well.
|
|||
|
||||
== Known changes
|
||||
|
||||
=== Overriding Delayed Identity Insert Behavior
|
||||
=== Type system / custom types
|
||||
|
||||
In Hibernate 5.3, we added support for `DelayedPostInsertIdentifier` behavior to be influenced based on the
|
||||
`FlushMode` or `FlushModeType` values, in short enhancing Extended PersistenceContext support. Unfortunately,
|
||||
there were a few side effects that were recently reported with this change.
|
||||
* General read-by-position
|
||||
* Other
|
||||
|
||||
In Hibernate 5.4, we wanted to preserve as much of the 5.3 behavior as possible and only restore very specific
|
||||
`DelayedPostInsertIdentifier` behavior for selected use cases.
|
||||
|
||||
We understand mappings can be complex and there very well could be a corner case we didn't consider. In order
|
||||
to make 5.4 as flexible with these changes as possible, we added a configuration option that you can use as a
|
||||
_temporary_ solution to completely disable the 5.3 behavior, reverting it back to 5.2 and prior.
|
||||
=== SQM
|
||||
|
||||
`hibernate.id.disable_delayed_identity_inserts=true`
|
||||
* Functions
|
||||
* Multi-table bulk manipulation HQL/Criteria query handling
|
||||
|
||||
If you find you need to use this configuration setting, be sure to report the mapping to us in a JIRA issue so
|
||||
that we can review it and determine if the mapping corner case should be included in our algorithm since the
|
||||
configuration setting is meant to bridge behavior support for this across a few releases.
|
||||
|
||||
=== Hibernate Spatial depends on JTS 1.16
|
||||
|
||||
Hibernate Spatial depends on the https://github.com/locationtech/jts[Java Topology Suite (JTS)]. In 5.4 this
|
||||
dependency has been upgraded to version 1.16. This implies a change in package naming:
|
||||
all `com.vividsolutions.jts.\*` packages have been renamed to `org.locationtech.jts.*`.
|
||||
|
||||
See https://github.com/locationtech/jts/blob/master/MIGRATION.md[the JTS Migration guide] for more information.
|
||||
|
||||
=== SQL Server JDBC Driver version upgrade to at least 6.1.2
|
||||
|
||||
Due to fixing https://hibernate.atlassian.net/browse/HHH-12973[HHH-12973], you need to upgrade the JDBC Driver version to at least 6.1.2. Due to https://github.com/Microsoft/mssql-jdbc/issues/91[this bug], the older versions of the SQL Server JDBC Driver cannot introspect the `INFORMATION_SCHEMA.SEQUENCES` without closing the database connection.
|
||||
|
|
Loading…
Reference in New Issue