I am afraid I have come to a Hibernate bug and I am wondering if someone might have an other explanation before I try to generate a test case.
I have a class which contains a simple parent-child relation to itself. If I fetch this class via the Criteria API without any ordering (addOrder) all the entities are fetched with a single select query. The same fast response I get with an ascending ordering for any property. If I want to fetch with a descending ordering I get a N+1 selection phenomenon. Hibernate is fetching every single entity separately then. I have turned on debugging and I am familiar with diving into source of Hibernate in a debugger. But till now I did not find the clue why Hibernate is changing its fetching strategy depending on the different ordering. Do you have a tip where to look for? Which Loader is responsible for decision how to fetch?

Thanks
Thomas