1) You are using property paths in conjunction with join fetches. Not sure that has ever been explicitly supported. But, should probably result in a specific exception if we don't want to support that combo. What I mean is that, your query:
original-query
SELECT user
FROM User user
LEFT OUTER JOIN FETCH user.contact
LEFT OUTER JOIN FETCH user.contact.emailAddresses2
LEFT OUTER JOIN FETCH user.contact.emailAddresses
really ought to be written:
original-query
SELECT user
FROM User user
LEFT OUTER JOIN FETCH user.contact c
LEFT OUTER JOIN FETCH c.emailAddresses2
LEFT OUTER JOIN FETCH c.emailAddresses
2) I made that change, but found that then we hit HHH-5465
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
There are 2 things in this test case...
1) You are using property paths in conjunction with join fetches. Not sure that has ever been explicitly supported. But, should probably result in a specific exception if we don't want to support that combo. What I mean is that, your query:
really ought to be written:
2) I made that change, but found that then we hit HHH-5465