In Relation To

It has been years in the making, but ORM 6.0 Final has finally been released!

This announcement will discuss the major changes, as well as give insight into why certain choices were made.

We will also be following up with a series of more focused posts targeting specific improvements or cool new features. Stay tuned!

The second candidate release for Hibernate ORM 6.0 has been released.

We fully expect this to be the last release candidate and currently plan on having the 6.0 final release within the next 2-4 weeks.

This release was held up a bit working on passing the Jakarta Persistence TCK. Mainly we had to wait for our challenges and proposed challenges to be discussed and accepted. This release fully passes the 3.1 TCK! Hopefully we will soon pass the 3.0 TCK as well, but we are still waiting on resolution of some challenges there.

The first candidate release!

Hibernate ORM 6.0.0.Beta3 has been released. Just in time for the holidays!

We are especially excited for this release because it feels like the last beta on the long journey it has taken to develop 6.0. Lots of work has gone into Beta3, but like Beta2 most of that work has been behind the scenes. A few specific things of note:

The second Beta of Hibernate ORM 6.0 has just been released.

Quite a lot has gone into this release, but at a high level -

The first Beta of Hibernate ORM 6.0 has just been released.

We had a few main focuses for this Beta:

Hibernate ORM 6.0 Alpha9 has just been released.

The main design goal for 6.0 is to improve even more Hibernate’s through-put performance. High-load performance testing showed Hibernate’s approach of reading values from ResultSet by name to be its most limiting factor in scaling throughput. At its most basic, 6.0 is all about changing from its old strategy of read-by-name to read-by-position. But that simple goal has a lot of ramifications.

With Alpha9, the APIs are really starting to stabilize which is great.

Hibernate ORM 6.0 Alpha6 has just been released.

The main design goal for 6.0 is to improve even more Hibernate’s through-put performance. High-load performance testing showed Hibernate’s approach of reading values from ResultSet by name to be its most limiting factor in scaling throughput. At its most basic, 6.0 is all about changing from its old strategy of read-by-name to read-by-position. But that simple goal has a lot of ramifications.

This Alpha6 release includes:

We are excited to announce the release of Hibernate ORM 6.0 Alpha5.

The main design goal for 6.0 is to improve even more Hibernate’s through-put performance. High-load performance testing showed that Hibernate’s approach of reading values from ResultSet by name to be its most limiting factor in scaling through-put. At its most basic, 6.0 is all about changing from its old strategy of read-by-name to read-by-position. But that simple goal has a lot of ramifications.

We have come really far, but still it is an Alpha, so there is still plenty more to do.

We are excited to announce the release of Hibernate ORM 6.0 Alpha4.

The main design goal for 6.0 is to improve even more Hibernate’s through-put performance. High-load performance testing showed that Hibernate’s approach of reading values from ResultSet by name to be its most limiting factor in scaling through-put. At its most basic, 6.0 is all about changing from its old strategy of read-by-name to read-by-position. But that simple goal has a lot of ramifications.

We have come really far, but still it is an Alpha, so there is still plenty more to do.