Hello,

We are in the process of upgrading from Hibernate 3.2 to either Hibernate 3.6.10 or 4.x. Unfortunately, HQL queries as the following one:


generate incorrect queries (with both Oracle10gDialect and DB2Dialect) like the following one:

(In Hibernate 3 Oracle10gDialect or DB2Dialect, in hibernate 4 is similar and also incorrect).




Notice this works correctly if we use explicit joins but due to our huge codebase and the dynamic nature of many of our queries this would be an extremely costly task.

Is this a bug in Hibernate 3.5-3.6-4? According to the documentation navigating through deferencing via dot notation should work; is there any in-depth documentation about the cases in which implicit joining works and the cases in which it doesn't? I cannot find any documentation or bug report about this behaviour.

BTW, If you think I'm just being stupid, tell me :)

I don't know if my original question was clear enough. The problem is that , when using "SELECT DISTINCT ChildObject from ParentObject " ordering by a field of the ChildObject without an explicit Join (ORDER BY ParentObject.ChildObject.Description ) , the SQL query that Hibernate builds has two INNER JOINS to the second table, or an INNER JOIN + a cartesian product including the second table.

select ... from PARENT_TABLE parent inner join CHILD_TABLE1 child1 on parent.ID_CHILD =child1.ID_CHILD inner join CHILD_TABLE2 child2 on parent.ID_CHILD =child2.ID_CHILD (Hibernate 4)
select ... from PARENT_TABLE parent inner join CHILD_TABLE1 child1 on parent.ID_CHILD =child1.ID_CHILD , CHILD_TABLE2 child2 where parent.ID_CHILD =child2.ID_CHILD (Hibernate 3.5+)

This works seamlessly if we use an explicit join in SQL rather than using parent.child.Description. Is this a problem in our query ? It used to work in Hibernate 3.2 .