Hibernate ORM 6.2.0 Final has just been released.
In many ways, this release marks the final step for the major forcus of 6.x centered around changing how Hibernate generates SQL. Many improvements in this release, as well as 6.0 and 6.1, have been implemented on top of this SQL AST work. As of 6.0 and 6.1, Hibernate used this SQL AST for loading state from the database. With 6.2, Hibernate also uses SQL AST for writing to the database.
Hibernate ORM 6.2.0.CR3 has just been released. It contains 64 resolutions, including 37 bug-fixes. Many of these improvements come directly from the excellent feedback and bug reports we continue to get from the community. Thank you again for the continued support and feedback!
Hibernate ORM 6.2.0.CR2 was just released with lots of goodies.
A little over a month has gone by since 6.2 CR1 was released. In that time, and even before, we’ve recieved really excellent feedback and bug reports and resolved over 100 Jira reports. Thanks for the feedback!
The code has really stabilized as the SQL AST changes smoothed out as well.
Hibernate ORM 6.2.0.CR1 was just released which contains a lot of new features, enhancements and bug-fixes.
[ ... ]
Hibernate ORM 6.0 makes mapping UUID values easy, including use of generated UUID values as identifiers.
By default, Hibernate will map
UUID values to either
a database-specific UUID type, if one -
UNIQUEIDENTIFIERfor T-SQL variants, etc.
BINARYif the database does not define a specific UUID type.
[ ... ]
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!