Hibernate version: 3.2.2

I'm using the Criteria API to dynamically perform joins with multiple associated collections. In the generated SQL I find that for each dynamically associated entity, there's a left outer join (which is expected), and in addition an "order by" clause as well on the respective foreign keys of associated collections. Is there a reason for the additional order by clauses? Because of this, the sort criteria that the client (a list display in web tier) specifies are not effective, and sorting of the result set does not happen as expected.

Sorting works fine if I use FetchMode.SELECT instead of JOIN, but that leads to a performance issue with too many queries being generated.

Can anyone shed some light on this?

Hi Spartacus,
Looks like this is an issue in hibernate .

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



Thx,
Alok.