biso,
See http://opensource.atlassian.com/project ... e/HHH-3524, someone posted a workaround by using left joins on createCriteria/createAlias.

I realize that this post is 5 years old, however it comes up top in google searches for "criteria api eager fetch" and there have been some posts as recent as 2010.

To Gavin:

Your post was indeed explicit, but utterly utterly unhelpful. (And a touch arrogant too.)
Why is it a "Bad Thing"?
What does using ALIAS_TO_ENTITY_MAP do for us in terms of eager fetching, that cannot be done by loading a collection eagerly at query time?

Stewart

This is correct behavior and will certainly not be changed.

What's that supposed to mean? Are you quoting gavin or attempting to explain somthing?

Thank you for your post Stewart. I registered for this forum just to agree with you.

I don't understand why Gavin would be so consistently rude. It's strange that someone who has dedicated so much of his time to providing community tools would then be so surprisingly unhelpful and condescending to his users on this forum. I have come up to speed with Hibernate over the last year and have been very pleased with it for the most part. But I have also learned to expect nothing but arrogant, unhelpful responses from the "Hibernate Team" on this board.

Gavin, we know you are brilliant. Just imagine that you are teaching kindergarten and need to exercise patience and restraint with your young charges. You don't need to beat them as if they were all eating the paste.

I worked around the same problem using

I don't know if it is a bad thing too
I hope it helps

Sorry (to the other readers) for the previous big red post but i am very pissed. To sum up, for anyone who stumbles up this:


- Nora's solution works, it's ok, do that to get the normal result when doing an alias
- Gavin King's post, that, in fact, the original behaviour is normal, is complete crap and here's why:

I've wasted 1 whole day debugging hibernate, the objects that are returned and the sql issued when you do a criteria.createAlias(associationPath, alias). It issues an inner join. The associated persistence bag is initialized, all the needed values are threre. Yet, when you access somethign on that association it will issue another select to retrieve it, even tho the data is already fetched. In the scenario I'm working now, these n+1 selects ended up in an application response time which was about 2x - 3x time slower then when they were removed. How can issuing an uncontrolled bunch of extra queries to get data that was already fetched be considered normal behaviour


Hibernate has tons of bugs, some of which exists for years now. The jpa implementation is probably the crappiest of them all. There are clear JPA specs and behaviours, that work as expected in Eclipse Link JPA implementation and which simply crash with weird stack traces in Hibernate jpa implementation. This is true of JPA1 and JPA2 implementations. I've stumbled upon tons of these while studying for the JPA exams, while trying the same things with eclipse link and hibernate. Some of them have JIRAs raised, most of them do not. Most of the ones with JIRAs are in "this is not a bug" or "this will not be fixed" statuses.

Sorry readers, but I think it's understandable why I'd get so pissed under such circumstances.

My advice. Use eclipselink JPA2. Not because it's better (it is), but because IT ACTUALLY DOES WHAT IT SAIS IT DOES.

LOL, comedy gold.

This works!