Hibernate version:
3.0.5 & 3.1rc2

Code between sessionFactory.openSession() and session.close():


I would expect that all Orders of the Customer are "eagerly" fetched in a second select. But it makes no difference, if FetchMode.SELECT is set or not.

A possible workaround is executing either Hibernate.initialize(customer.getOrders()) or customer.getOrders().size() but this is not practical for more complex graphs.

The same query also works fine with a FetchMode.JOIN.

Maybe my topic was a little unclear -- I'll add a simple question:

Has anybody here used FetchMode.SELECT successfully on Criteria-Queries?

Nobody?

Could someone from the Hibernate Team please write a comment, or should I attach a complete test case first (It's very basic....) ?

Thanks.

I'll continue my monologue...

In the meantime, I got it. The javadoc comment of FetchMode.SELECT ("Fetch eagerly, using a separate select.") is obviously misleading. The reference docs state the opposite logic.

But I still think there should be a FetchMode for immediate fetching associations mapped as lazy - without using FetchMode.JOIN.

Is there any chance for a Feature Request?


Feel free to answer me - you could earn a credit.

:)

hi,

I encounter the same problem as you are.
I see no effect to the FetchMode.LAZY (more than lazy fetch), I don't understand the comment which states that it's a eager fetch...
I would be glad to have an answer from the hibernate team.

cheers,

eric

We're looking for the same functionality - loading an association's collection through an immediate select. So far we have not found a way to do it with the Criteria query. Using an outer join doesn't work for us because it breaks paging...

http://opensource.atlassian.com/project ... e/HHH-1211

~Ganesh