Tags
Authors
Hibernate Reactive 3.0.0.Beta2 is now available!
This release is compatible with Hibernate ORM 7.0.0.Beta4, and upgrades the Vert.x SQL client to 4.5.13.
It also contains a couple of bug fixes:
The full list of changes is available on GitHub.
The fourth beta release of Hibernate 7 is now available.
Along with many bugfixes and minor improvements, this release features the following enhancements:
-
The brand-new
Restriction,Path, andRangeAPIs make it easy to add programmatic restrictions to HQL queries or Jakarta Data repository methods in a completely type-safe way. -
The package
org.hibernate.graphwas completely re-engineered, fixing a number of long-standing issues with our implementation of the Jakarta PersistenceEntityGraphAPI. -
StatelessSessionis now able to make use of the second-level cache, reflecting the changing role of this very important API in the Hibernate ecosystem. -
Reactive repositories backed by Hibernate Reactive are now a documented feature of Hibernate Data Repositories.
-
The
hibernate-jfrmodule was enhanced to send more events to Java Flight Recorder. -
HQL now provides portable
sha(),md5(), andhex()functions. -
Hibernate Processor now features much better support for inner classes.
Hibernate Reactive 2.4.5.Final is now available!
This release is compatible with Hibernate ORM 6.6.7.Final, and upgrades the Vert.x SQL client to 4.5.12.Final.
It also contains a couple of bug fixes:
The full list of changes is available on GitHub.
Last week, Jeroen Borgers asked on Twitter for a standard way to set the JDBC fetch size in JPA, that is, for Hibernate’s Query.setFetchSize() to be added to the standard APIs.
This took me slightly by surprise, because nobody has ever asked for that before, but I asked him to go ahead and open an issue.
After some discussion, I think I’m satisfied that his actual needs can be met in a different way, but the discussion did help to draw my attention to something important: the default JDBC fetch size for the Oracle driver is 10.
Now, I would never pretend to be an expert in Oracle performance tuning, and I don’t use Oracle every day. Even so, I felt like this is something that I definitely should have known off the top of my head, after so many years working with JDBC.
Out of curiosity, I ran a poll on Twitter, which was shared by Franck Pachot among others:
Hibernate Reactive 2.4.4.Final is now available!
This release is compatible with Hibernate ORM 6.6.5.Final.
It also contains a couple of bug fixes:
The full list of changes is available on GitHub.
Hibernate Reactive 2.4.3.Final is now available!
This release is compatible with Hibernate ORM 6.6.4.Final.
The full list of changes is available on GitHub.
We just published Hibernate Search 8.0.0.Alpha1, the first alpha release of the next major version of Hibernate Search.
This version brings metric aggregations, logging improvements, a new Lucene backend and more.
Hibernate Search 8.0 sets JDK 17 as a baseline and is no longer compatible with JDK 11.
It also upgrades Lucene and Hibernate ORM dependencies and includes compatibility with the latest Elasticsearch and OpenSearch versions.
Hibernate Reactive 3.0.0.Beta1 is now available!
This release is compatible with Hibernate ORM 7.0.0.Beta3.
The full list of changes is available on GitHub.
We just published Hibernate Validator 9.0.0.CR1, the first candidate release of the new 9.0 series of Hibernate Validator.
This series targets Jakarta EE 11. It is the implementation of the Jakarta Validation 3.1.
Since the previously released 9.0.0.Beta3, we spent some time on various build improvements, tidied up a few things and addressed various reports from the community and our testing.
With this release, we no longer publish relocation POMs for the old org.hibernate group id.
There also are some dependency updates and bug fixes.
Hibernate Validator 8.0.2.Final maintenance release is out.
This release contains some documentation and constraint violation message translation updates as well as a few bug fixes.
