|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
(No you didn't. No one responded - that's why I tested and reported.)
Correct me if my memory fails me, but JoinFragment.LEFT_OUTER_JOIN overrides the fetch mode in the mapping doesn't it? (In support of my memory, I seem to get the same result with fetch="select")
And yes, we have real life cases where we need left outer join (i.e. more like "find all orders with item 'X' on any order line, or no order lines at all"; but in reality with more levels, as of HHH-6877). Maybe that is too specific to be supported by Hibernate Criterias???