Hibernate version: 3.2.6

In the reference documentation it says:

"By default, Hibernate3 uses lazy select fetching for collections and lazy proxy fetching for single-valued associations"

Has the fetching strategy for single-valued associations changed in version 3.2.x?

I use the following example:




Then when I execute the following code in the debugger:



or



in both cases the address field is not a proxy, but the address object contains all address information from the database. So the address is eager loaded.
I know that this is the default behaviour for JPA, but is this also the default behaviour of hibernate?
If yes, then the reference documentation is not correct.
If no, then why do I get this behaviour in my example program?

Thanks,

Rene

In order to enable lazy loading in the one to one mapping you need to tell hibernate that the entity in the other end of association always exist. So that when the hiberante actually initializes the proxy it won't get "object not found" kind of excpetion. In hibernate mapping you do this by specifying contrained="true".

Well, my question was actually:

What is the default fetching behaviour of Hibernate for single-valued associations (One-to-one or Many-to-one)?

I thought that Hibernate was alway's lazy, but from the example in my previous post, it shows that the one-to-one association is eagerly loaded.