Re: [eclipselink-users] eager as default for @xxxToOne

[Hebert Coelho <hebolive@xxxxxxxxx>]

Hello Yannick,

My guess is that to bring a *One relationship from the database is because it is a "cheap" behavior. Usually it will not overhead the processor or the network.

But this is my guess, I believe that some of the JPA creators could answer that better.

Regards

On 12/29/2014 03:18 PM, Yannick Majoros wrote:

Hello Hebert,

Thanks for your answer. The discussion I've been involved in our why this is the default, as stated by the spec. Is this just for historical reasons. And if it isn't, what is the reasoning behind that?

Thanks,

Yannick

Le lun. 29 déc. 2014 14:17, Hebert Coelho <hebolive@xxxxxxxxx> a écrit :

Hello Yannick,

Because it is written in the spec. (:





Take a look at the spec in the section 11.1 that details the annotations and its defaults.

On 12/28/2014 06:54 PM, Yannick Majoros wrote:

Hello,

As a reaction to http://java.dzone.com/articles/eager-fetching-code-smell , could someone explain why EAGER is the default fetch type for @xxxToOne relations?

Thanks,

Yannick Majoros

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipselink-users