From 7b3570149df73e8d80d065a3596cdd301d2e1802 Mon Sep 17 00:00:00 2001 From: Steve Ebersole Date: Tue, 3 May 2016 12:21:11 -0500 Subject: [PATCH] HHH-10664 - Prep 6.0 feature branch - merge hibernate-entitymanager into hibernate-core (test fixup) --- migration-guide.adoc | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+), 8 deletions(-) diff --git a/migration-guide.adoc b/migration-guide.adoc index 54ee496744..e8a086a058 100644 --- a/migration-guide.adoc +++ b/migration-guide.adoc @@ -1,12 +1,21 @@ -= 6.0 Migration Guide += 5.2 Migration Guide :toc: -This guide discusses migration from Hibernate ORM version 5.1 to version 6.0. For migration from +This guide discusses migration from Hibernate ORM version 5.1 to version 5.2. For migration from earlier versions, see any other pertinent migration guides as well. +== Background + +Lots of work has been done for 6.0. One of the things 6.0 will need is a unified view of "type systems" +including its own type system (Type, EntityPersister, CollectionPersister, etc) and JPA's type system - which +would mean unifying all of this in hibernate-core. Because of this and the other large changes slated for 6.0 +we decided to release a 5.2 that showed a clear migration path to the changes in 6.0 but that still supported the +older calls and expectations as much as possible. + + == Move to Java 8 for baseline -Hibernate 6.0 is built using Java 8 JDK and will require Java 8 JRE at runtime (we are investigating whether +Hibernate 5.2 is built using Java 8 JDK and will require Java 8 JRE at runtime (we are investigating whether Java 9 will also work). This has a number of implications: * The hibernate-java8 module has been merged into hibernate-core and the Java 8 date/time types are now natively @@ -51,10 +60,6 @@ implement JPA methods now in core I decided to implement more of a composition a has been moved into the `org.hibernate.Cache` and `org.hibernate.engine.spi.CacheImplementor` contracts helping implement JPA's `javax.persistence.Cache` role. -== SQM - -todo - discuss - == Misc @@ -67,4 +72,5 @@ todo - discuss are allowed to access EntityTransactions. Need a strategy to handle this * Session#getFlushMode and Query#getFlushMode clash in terms of Hibernate (FlushMode) and JPA (FlushModeType) returns. #getFlushMode has been altered to return JPA's FlushModeType. The Hibernate FlushMode - is still available via #getHibernateFlushMode and #setHibernateFlushMode \ No newline at end of file + is still available via #getHibernateFlushMode and #setHibernateFlushMode. Same for Session#getFlushMode + and EntityManager#getFlushMode. \ No newline at end of file