Hibernate's core Object/Relational Mapping functionality
Today, we published a new maintenance release of Hibernate ORM 6.2: 6.2.12.Final.
This release introduces a few minor improvements as well as bug fixes.
You can find the full list of 6.2.12.Final changes here.
For additional details, see:
See also the following resources related to supported APIs:
@Incubating)@Deprecated + @Remove)@Internal)Visit the website for details on getting in touch with us.
Today, we published a new maintenance release of Hibernate ORM 6.2: 6.2.11.Final.
This release introduces a few minor improvements as well as bug fixes.
You can find the full list of 6.2.11.Final changes here.
For additional details, see:
See also the following resources related to supported APIs:
@Incubating)@Deprecated + @Remove)@Internal)Visit the website for details on getting in touch with us.
5.2.0 includes many improvements and bug-fixes. For a complete list of changes, see https://hibernate.atlassian.net/projects/HHH/versions/23150/tab/release-report-done.
Many of the changes in 5.2.0 have important ramifications in terms of both usage and extension. Be sure to read the 5.2 Migration Guide for details.
Below is a discussion of the major changes.
5.2 moves to Java 8 as its baseline. This means:
hibernate-java8 module has been removed, and that functionality has been moved into hibernate-core.java.util.stream.Stream) query results.java.util.Optional as return from methods that may return null.hibernate-core.That effectively means that the hibernate-entitymanager module no longer exists. Its functionality being consumed into hibernate-core.
Support for using any JCache-compliant cache impl as a second-level caching provider.
Support has been added for specifying a batch size for write operations per Session.
The 5th bug-fix release for Hibernate ORM 5.0. This release and the upcoming 5.0.6 release have been done on an accelerated time-box of 2 weeks (from the normal 4 weeks for bug-fix releases) due to US holidays.
The complete list of changes can be found here (or here for people without a Hibernate Jira account).
For information on consuming the release via your favorite dependency-management-capable build tool, see http://hibernate.org/orm/downloads/
For those of you allergic to dependency-management-capable build tools, the release bundles can be obtained from SourceForge or BinTray.
The fourth bug-fix release for Hibernate ORM 5.0
There are 52 issues resolved in this release. 20 of those came out of the recent Jira cleanup. Initially that initiative pulled in roughly 750 issues. To date, 66 of those have been resolved - fixed or verified as out-of-date, unable-to-reproduce, etc. An additional 14 have been more properly reclassified as feature or enhancement requests rather than bugs. The really cool part is the amount of community help we have gotten in making that happen! Thanks to everyone responding, verifying and even fixing alot of these bugs!
The complete list of changes can be found here. People without a Hibernate Jira account will not be able to access the previous link and can access the changelog in GitHub; the issue I reported with Atlassian has been resolved and is ready for deployment into our hosted environment, I just do not know when that will happen.
For information on consuming the release via your favorite dependency-management-capable build tool, see http://hibernate.org/orm/downloads/
For those of you allergic to dependency-management-capable build tools, the release bundles can be obtained from SourceForge or BinTray.
http://in.relation.to/2015/10/28/hibernate-orm-503-final-release/
* [HHH-1400] - formula-based property leads to generation of invalid SQL with subselect fetches
* [HHH-9074] - HQL Query with boolean and @Convert
* [HHH-9374] - EntityGraph applied to subquery when using collection function
* [HHH-9784] - scroll() and iterate() methods do not support provided HQLQueryPlan
* [HHH-10104] - Using JPA 2.1 schema generation together with hbm2ddl runs into deadlock with MySQL
* [HHH-10169] - Hibernate ignores foreign-key name in hbm <joined-subclass>
* [HHH-10170] - Reuse JAXBContext instance (Slow mapping initialization) - port HHH-10065 fix to 5.0 branch
* [HHH-10172] - Throw MappingException when entity/component class defines multiple matching getters by stem name
* [HHH-10174] - Incorrect splitting of string using dot as separator
* [HHH-10180] - hbm2ddl tools cannot generate create/update script not modifying the database
* [HHH-10188] - "stored" is a reserved keyword in MySQL 5.7
* [HHH-10189] - NPE in InformationExtractorJdbcDatabaseMetaDataImpl
* [HHH-10193] - NameQualifierSupport for Hypersonic should be catalog
* [HHH-10194] - Change NameQualifierSupport for Hypersonic from CATALOG to SCHEMA
* [HHH-10195] - QueryHintSQLServer2012Test is wrong
* [HHH-10196] - DefaultGeneratedValueTest fails on MySQL
* [HHH-10197] - SchemaManagementException when performing SchemaUpdate
* [HHH-10206] - Primary key not created for a Set after loading from XML mapping file
* [HHH-10207] - Constraint name not considered for a Set while loading from XML mapping file
* [HHH-10217] - ModelBinder fails to bind version property when generated="always"
* [HHH-10137] - Upgrade to/support Jandex 2.0
* [HHH-10153] - Upgrade to Gradle 2.7
* [HHH-10087] - Support prepending of locks
* [HHH-10190] - org.hibernate.engine.spi.ActionQueue#executeActions() optimization
The complete list of changes can be found here.
For information on consuming the release into your build via your favorite dependency-management-capable build tool, see http://hibernate.org/orm/downloads/.
For those of you allergic to dependency-management-capable build tools, the release bundles can be obtained from SourceForge or BinTray.
The complete list of changes can be found here.
For information on consuming the release into your build via your favorite dependency-management-capable build tool, see http://hibernate.org/orm/downloads/.
For those of you allergic to dependency-management-capable build tools, the release bundles can be obtained from SourceForge or BinTray.
Today I have released Hibernate ORM 5.0 (5.0.0.Final). This has been a long time coming and is the result of the efforts of many folks. Thanks to everyone who helped us get here with fixes, bug reports, suggestions, input and encouragement!
A lot of development has gone into 5.0. Here are the big points:
The venerable way to bootstrap Hibernate (build a SessionFactory) has been to use its Configuration class. Configuration, historically, allowed users to iteratively add settings and mappings in any order and to query the state of settings and mapping information in the middle of that process. Which meant that building the mapping information could not effectively rely on any settings being available. This lead to many limitations and problems.
5.0 introduces a new bootstrapping API aimed at alleviating those limitations and problems, while allowing better determinism and better integration. See the Bootstrap chapter in the User Guide for details on using the new API.
Configuration is still available for use, although in a limited sense. Some of its methods have been removed. Under the covers Configuration makes use of the new bootstrap API.
Hibernate Spatial is a project that has been around for a number of years. Karel Maesen has done an amazing job with it.
Starting in 5.0 Hibernate Spatial is now part of the Hibernate project proper to allow it to better keep up with
upstream development. It is available as org.hibernate:hibernate-spatial. If your application has need for
GIS data, we highly recommend giving hibernate-spatial a try.
Well, ok.. not all of Java 8. Specifically we have added support for Java 8 Date and Time API in regards to easily mapping attributes in your domain model using the Java 8 Date and Time API types to the database. This support is available under the dedicated hibernate-java8 artifact (to isolate Java 8 dependencies). For additional information, see the Basic Types chapter in the Domain Model Mapping Guide.
JPA defines support for GenerationType#AUTO limited to just Number types. Starting in 5.0 Hibernate offers expandable support for a broader
set of types, including built-in support for both Number types (Integer, Long, etc) and UUID. Users are also free to plug
in custom strategies for interpreting GenerationType#AUTO via the new org.hibernate.boot.model.IdGeneratorStrategyInterpreter extension.
NamingStrategy has been removed in favor of a better designed API. 2 distinct ones actually:
org.hibernate.boot.model.naming.ImplicitNamingStrategy - used whenever a table or column is not explicitly named to determine the name to useorg.hibernate.boot.model.naming.PhysicalNamingStrategy - used to convert a "logical name" (either implicit or explicit) name of a table or column
into a physical name (e.g. following corporate naming guidelines)5.0 offers significantly improved support for JPA 2.1 AttributeConverters:
Support for "bulk id tables" has been completely redesigned to better fit what different databases support.
The transaction SPI underwent a major redesign as part of 5.0 as well. From a user perspective this generally
only comes into view in terms of configuration. Previously applications would work with the different backend
transaction stratagies directly via the org.hibernate.Transaction API. In 5.0 a level of indirection has been
added here. The API implementation of org.hibernate.Transaction is always the same now. On the backend, the
org.hibernate.Transaction impl talks to a org.hibernate.resource.transaction.TransactionCoordinator which represents
the "transactional context" for a given Session according to the backend transaction strategy. Users generally do not
need to care about the distinction.
The change is noted here because it might affect your bootstrap configuration. Whereas previously applications would
specify hibernate.transaction.factory_class and refer to a org.hibernate.engine.transaction.spi.TransactionFactory FQN,
with 5.0 the new contract is org.hibernate.resource.transaction.TransactionCoordinatorBuilder and is specified using the
hibernate.transaction.coordinator_class setting. See org.hibernate.cfg.AvailableSettings.TRANSACTION_COORDINATOR_STRATEGY
JavaDocs for additional details.
The following short-names are recognized:
jdbc::(the default) says to use JDBC-based transactions (org.hibernate.resource.transaction.backend.jdbc.internal.JdbcResourceLocalTransactionCoordinatorImpl)
jta::says to use JTA-based transactions (org.hibernate.resource.transaction.backend.jta.internal.JtaTransactionCoordinatorImpl)
See the User Guide for additional details.
5.0 offers much improvement in the area of schema tooling (export, validation and migration).
Hibernate's native APIs (Session, etc) have been updated to be typed. No more casting!
Really this started with a frustration over the fragility of hibernate-osgi tests. The first piece was a better testing setup using Pax Exam and Karaf. This lead to us generating (and now publishing!) a Hibernate Karaf features file.
OSGi support has undergone some general improvement as well thanks to feedback from some Karaf and Pax developers and users.
See the Getting Started Guide for additional details on using the new Karaf features file.
A lot of work has gone into the documentation for 5.0. Its still not complete (is documentation ever "complete"?), but it is much improved.
See the revamped http://hibernate.org/orm/documentation/5.0[documentation page] for details.
For now the plan is to publish the release bundles (zip and tgz) to BinTray. We will continue to publish to SourceForge as well. For the time being we will publish the bundles to both.
Ultimately we will start to publish the "maven" artifacts there as well.
This is all a work in progress.
See http://hibernate.atlassian.net/projects/HHH/versions/20851 for the complete list of changes.
See http://hibernate.org/orm/downloads/ for information on obtaining the releases.
The fourth candidate release for Hibernate ORM 5.0 (5.0.0.CR4). The purpose was entirely to change the defaults for some settings. This allowed some additional fixes and additional documentation work to make it in.
The default ImplicitNamingStrategy (hibernate.implicit_naming_strategy) has changed to the JPA-compliant one. Additionally added some short-names for the Hibernate-provided implementations.
The previous default was "legacy-jpa". Existing applications that previously used the default naming strategy
and want to continue to use that implicit naming strategy should specify hibernate.implicit_naming_strategy=legacy-jpa in their configuration settings. Alternatively, they can call MetadataBuilder#setImplicitNamingStrategy(ImplicitNamingStrategyLegacyJpaImpl.INSTANCE).
Back in 3.6 I developed a new set of identifier generator strategies aimed at database portability based on the JPA expectations for @SequenceGenerator and @TableGenerator. Between 3.6 and now the default has been to continue to use the legacy generator strategies, but we added a setting (hibernate.id.new_generator_mappings) to allow applications to request the newer strategies be used. The default for this setting had been false. The default is now true.
Existing applications updating to CR4 and then Final that experience issues with identifier generator strategy selection should try setting this back to false if they wish to keep using the legacy mappings.
This is a new feature in 5.0, but previously the default had been to auto-quote any sql identifiers believed to be a keyword in the underlying database. That feature has been disabled by default.
Applications that wish to use this feature should explicitly enable it by specifying hibernate.auto_quote_keyword=true in their configuration settings.
Still in progress, but alot more content has been added.
Additionally many other improvements and bugfixes are included. See https://hibernate.atlassian.net/projects/HHH/versions/20752 for the complete list of changes.
The release tag is available at https://github.com/hibernate/hibernate-orm/releases/edit/5.0.0.CR4
As always, see http://hibernate.org/orm/downloads/ for information on obtaining the releases.