This is not necessarily needed for 5.3.0, but I would like to get it into
the 5.3 branch.
So far, there is one change to an SPI, Queryable#lazyGroupSelectFragment is
added:
public String lazyGroupSelectFragment(
String tableAlias,
String suffix,
String fetchGroupName);
The method gets implemente
Hi Steve,
I was going to make an improvement to my POC to use lambda expressions. I
remember you had a couple of comments about the POC; I'll have to look them
up. If it wasn't anything that had a big impact on the design, then I think
I may be able to get it fixed in 2 weeks. I'll look into this
Hi,
Currently, when a lazy group is loaded that has associations, there are 2
SQL statements executed.
For example, suppose the DEFAULT lazy group contains the following:
* Order#customer is a lazy many-to-one association;
* Order#text is a lazy LOB.
When one of these properties is referenced
An update on this; I've found multiple issues, yet when digging none
seem to be a strong reason to withold switching to Byte Buddy as
default.
The main problem seems to be that running the testsuite will somehow
load 2.867 different Class instances all having the same name
"org.hibernate.test.byte
I'm ok with it, but only if it's going to be ready in 2 weeks
On Thu, Mar 1, 2018, 2:32 PM Gail Badner wrote:
> Hi,
>
> HHH-10478 is currently scheduled for 6.0.0.alpha1. What do you think about
> introducing it into 5.3.0 instead?
>
> Using an OperationContext would be a less hacky way to fix
Hi,
HHH-10478 is currently scheduled for 6.0.0.alpha1. What do you think about
introducing it into 5.3.0 instead?
Using an OperationContext would be a less hacky way to fix HHH-3799
(PersistentSet does not honor hashcode/equals contract when loaded eagerly).
It would be nice to remove operation-
In 2 weeks I will be releasing 5.3 CR2. I waned to start a unified
discussion about the remaining currently unresolved discussions and what
exactly we are going to do for 5.3 mainly in regards to compatibility with
an eye to 6.0
Cache region-name as exposed in API/SPI
This one is a "sneaky" co
Hi Petar,
You can use this template:
http://in.relation.to/2016/01/14/hibernate-jpa-test-case-template/
to create a test case that replicates the issue. You don't need to provide
all entities,
just the 4 entities that build that hierarchy you have mentioned in your
email.
If you can replicate i
Hi Christian,
My model has more than 250 entities big. Here's the code that throws the
NLP:
Class c1 = clazz1.getMappedClass();
Class c2 = commonPersistentClass.getMappedClass();
MappedSuperclass commonMappedSuperclass = null;
// First we traverse up the clazz2/commonPersistentClass super types
