Hi,
Do you remember why the JPA User Group decided to make the ManyToOne and
the OneToOne associations EAGER by default?
In Hibernate 3.x, these associations used to be LAZY, so there must have
been a reason for taking this decision.
Thanks,
Vlad
__
The Hibernate team argued against this, but we were outvoted. So... sorry
I cannot "justify it" ;)
Obviously as our previous default shows we believe the associations should
be lazy by default.
On Sun, Feb 28, 2016 at 11:00 AM Vlad Mihalcea
wrote:
> Hi,
>
>
> Do you remember why the JPA User
Thanks,
Rhe only reason I found is this paragraph:
"The EAGER default for OneToOne and ManyToOne is for implementation reasons
(more difficult to implement), not because it is a good idea. Technically
in JPA LAZY is just a hint, and a JPA provider is not required to support
it, however in reality
But to me that is not a reason EAGER is the default. As the passage says,
LAZY is just a hint. So for a provider that does not support LAZY, EAGER
would be used instead anyway. No, some of the EG members specifically
argued for wanting to-one associations to be EAGER by default. IMO it was
a ba
On 25 February 2016 at 16:25, Sanne Grinovero wrote:
> On 25 February 2016 at 15:37, Gunnar Morling wrote:
>> 2016-02-25 16:28 GMT+01:00 Sanne Grinovero :
>>> On 25 February 2016 at 15:14, Gunnar Morling wrote:
It's Monday morning.
Having at least rudimentary docs would be great,
Awesome! The docs look great, thanks a lot!
+100 for pushing this out, I think it's ready for that.
Cheers guys,
--Gunnar
2016-02-29 1:59 GMT+01:00 Sanne Grinovero :
> On 25 February 2016 at 16:25, Sanne Grinovero wrote:
>> On 25 February 2016 at 15:37, Gunnar Morling wrote:
>>> 2016-02-25
