|
||||||||
|
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 |
||||||||
After some time to reflect on this - I don't think this should be CLOSED, it is actually a bug in the loading order of find() and a Query is capable of doing things correctly. (For some reason it is always easy to accept an explanation of Hibernate's internals as a reason to CLOSE a bug report)
Perhaps when loading chains of Sets, Hibernate could store proxies in a List until sure that they have all been loaded, before creating the Set proxy. Or whatever Query does.