Eclipse Community Forums: EclipseLink

Help

Home

Home » Eclipse Projects » EclipseLink » hibernate gotchas

Show: Today's Messages :: Show Polls :: Message Navigator

hibernate gotchas [message #715979]

Tue, 16 August 2011 06:43

Tom Eugelink

Messages: 817
Registered: July 2009

Senior Member

I found this in a hibernate gotcha article and was wondering if the same applies to EclipseLink:

When mapping a relation as One-to-One or Many-to-One on the "One" side of the relation you can't have lazy loading unless you specify the field as not nullable.

Why is that?
Essentially on the many side of the relation hibernate can use collection proxies and lazily load instances when required.
On the "One" side there is no collection interface but instead a reference to one of your model classes.
Hibernate can proxy that one as well but only if it is sure the reference will never be null!

Tom

Report message to a moderator

Re: hibernate gotchas [message #716095 is a reply to message #715979]

Tue, 16 August 2011 12:54

Chris Delahunt

Messages: 1389
Registered: July 2009

Senior Member

That is a Hibernate specific limitation.

EclipseLink uses weaving (static or dynamic) to allow lazy relationships, so they can be nullable, as described here:
http://wiki.eclipse.org/Using_EclipseLink_JPA_Extensions_(ELUG)#What_You_May_Need_to_Know_About_EclipseLink_JPA_Lazy_Loading

Best Regards,
Chris

Report message to a moderator

Previous Topic:	(no subject)
Next Topic:	Howto log SQL with java.util.logging?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 16:50:25 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter