This guide discusses migration from Hibernate ORM version 5.3 to version 5.4. For migration from earlier versions, see any other pertinent migration guides as well.
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.
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.
hibernate.id.disable_delayed_identity_inserts=true
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 the 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 the JTS Migration guide for more information.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。