By Christian Beikov on 23 November 2018
I’m proud to announce that Blaze-Persistence version 1.3.0 is finally done!
It took so much longer than initially planned, mostly because of the great feedback we received that we simply deemed to be too important to be deferred. We felt that 1.3.0 would only be a partial solution without these fixes and features, so we decided to get those features in before releasing.
The most notable features and bug fixes are:
-
#667 Validate equals/hashCode implementations of JPA managed types used in entity views to avoid errors due to wrong implementations
-
#571 Support binding embeddables and associations using compound or foreign keys in CTE’s and DML
-
#509 Make use of collection DML API for updatable entity views in flushing
-
#681 Allow updatable entity views to have multiple non-cascading parents
-
#434 Implement creatability validation for creatable entity views
-
#402 Special rendering of implicit joins in ON clause
-
#517 Validate inverse remove strategy SET_NULL against column nullability
-
#679 Spring Domain events related bug fixes
Take a look into the changelog for a full list of changes and improvements.
Once again I would like to thank Giovanni Lovato for all the issues he reported. He was testing out early implementations of the query flush strategy for updatable entity view collections and went through many test-debug cycles with me to get the implementation right for even the most complex JPA models. Without his feedback and patience, the release wouldn’t be as good as it is. Thanks for your contribution and keep up the good work!
Thanks to Jan-Willem Gmelig Meyling we caught up on changes coming with Hibernate 5.4 and adapted our implementations to be able to provide a consistent experience! One of these changes is that with Hibernate 5.4 you will now be able to leverage the single value id access optimization not only for primary ids, but also for natural ids.
With version 1.3.0 a.k.a. Fury being done, we will start working on 1.4.0 a.k.a. Coulson. We might port back critical fixes to 1.3, but in general we don’t anticipate to do any further public 1.3 releases. Since 1.4 is backwards compatible, it should be no problem to work with 1.4.0 Alpha releases to get fixes that were done on master.
If you need fixes back-ported, I would like to direct you to our commercial support.