[hibernate-issues] [Hibernate-JIRA] Issue Comment Edited: (HHH-5645) Criteria.createAlias with specified criterion results in wrong parameters passed into SQL statement

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5645?page=c... ] Paweł Szafran edited comment on HHH-5645 at 9/13/11 2:05 AM: ------------------------------------------------------------- Hi Fekete, Unfortunately, my team has faced the very same problem: We have a complex criteria query that has 3 joins defined by createAlias() with additional restrictions (to appear in on() clause). One of our testers found that the query returns wrong results. We investigated the problem and went to the exact same conclusions as you did: The order of joins in final sql statement doesn't match the list of values to be put in that statement! The order of joins in Java code is e.g. ABC, and so the values to be put in the sql statement are in the same ABC order, but the generated sql statement itself is somehow in ACB order, so the values are put in wrong places, and this produces the incorrect result. Of course, changing the order of calling createAlias() in the Java code to ACB, makes the query works fine, but it's not a solution - the order of using createAlias() shouldn't matter. This is really frustrating, especially that no one from Hibernate team replied to this issue. And it's been almost a year now! So in this case, I have to ask you Fekete: Have you found the solution to this problem? Or how did you solve this issue in your project? I would really appreciate your help! Best Regards, Pawel was (Author: pawel.jdfcafe): Hi Fekete, Unfortunately, my team has faced the very same problem: We have a complex criteria query that has 3 joins defined by createAlias() with additional restrictions (to appear in on() clause). One of our testers found that the query returns wrong results. We investigated the problem and went to the exact same conclusions as you did: The order of joins in final sql statement doesn't match the list of values to be put in that statement! The order of joins in Java code is e.g. ABC, and so the values to be put in the sql statement are in the same ABC order, but the generated sql statement itself is somehow in ACB order, so the values are put in wrong places, and this produces the incorrect result. Of course, changing the order of calling createAlias() in the Java code to ACB, makes the query works fine, but it's not a solution - the order of using createAlias() shouldn't matter. This is really frustrating, especially that no one from Hibernate team replied to this issue. And it's been almost a year now! So in this case, I have to ask you Fekate: Have you found the solution to this problem? Or how did you solve this issue in your project? I would really appreciate your help! Best Regards, Pawel -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira