----- Original Message -----
From: "Scott Marlow" <smarlow(a)redhat.com>
To: "Gail Badner" <gbadner(a)redhat.com>
Cc: hibernate-dev(a)lists.jboss.org
Sent: Thursday, October 13, 2011 9:53:23 AM
Subject: Re: [hibernate-dev] Needed for 4.0.0.CR5?
On 10/12/2011 06:12 PM, Gail Badner wrote:
> A couple of new issues were opened today that seem important enough
> to consider for 4.0.0.CR5. Not sure there's any time left to do
> this, but here they are:
>
> HHH-6727 (serializing an EntityManager should include enough
> information to later be unserialized with re-association to
> existing EntityManagerFactory (even on a different machine/jvm
> process))
>
https://hibernate.onjira.com/browse/HHH-6727
If this can be fixed in a non-disruptive fashion, it would be good to
assign to 4.0.0.next. If we don't fix in 4.0.0.next, I would like to
fix it soon after. At the very best, in a clustered environment or
one
that passivates/activates the extended persistence context, extra
memory
will be used by the duplicate EMF. Its not clear (to me), if the
second
level entity/query cache is also duplicated. If the cache is
duplicated
(when serializing/unserializing an EntityManager), I would like to
fix
sooner.
I've made the fix version 4.0.0.next. Let's discuss on
#hibernate-dev.
>
> HHH-6726 (Oracle : map TextType to clob and ImageType to blob)
>
https://hibernate.onjira.com/browse/HHH-6726
> There have been a number of issues opened since the change was made
> to map TextType (LONGVARCHAR) 'long' and ImageType (LONGVARBINARY)
> to 'long raw'. This change was already documented in the migration
> notes. Should the mapping for Oracle (only) be changed back to
> clob and blob?
>
> Steve, if you have a chance, please take a look at: HHH-6723
> (Remove extra join from eager @OneToOne). I created a pull request
> at:
https://github.com/hibernate/hibernate-core/pull/184. If
> possible, I'd like to restore the performance improvement of
> HHH-5109 for 3.6.8 and 4.0.0.CR5.
>
> Please let me know if I should look at any of this for CR5. I'll
> look into the Infinispan failure until I hear otherwise.
>
> Thanks,
> Gail
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev