Hi,

in http://forum.hibernate.org/viewtopic.php?t=958455, it is said that it is possible to use lazy loading for one-to-one mapping by turning 'optional' flag to false.

However, it does not seem to work for me, and there is a comment in http://www.hibernate.org/162.html stating that it is not possible to use it with JPA.

What is the status? Is it possible?

Note that I annotate attributes and not getters. I guess I should annotate the getter to allow Hibernate to intercept call and check the other side of the relationship exists. Shouldn't I?

Also, I don't understand why Hibernate loads the whole object on the other side of relationships, and not just check that there is 'something'.

Just checking would already help us.

Cheers,

J-F

AFAIK the wiki comment is wrong.

@OneToOne(optional=false) should to the trick

And field or getter use are irrelevant, both will work.

It does not work for us. I can still see the SQL statement retrieving the whole counterpart object.

I could mention that it is the 'weak' part (i.e. 'mappedBy') of a bidirectional association. Maybe it is related.

I would also appreciate if someone could shed some light on why Hibernate does not just check that the counterpart object exists, instead of loading it.

This is a real problem for us, because the counterpart object itself has eager relationships.

Cheers,

J-F

ah year mappedBy need to load the object since the FK is "on the other table".
The rational is that since a DB access is needed, it is preferable to load the object.

On a related note, EAGER in the mapping is usually not a good idea.