|
||||||||
|
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 |
||||||||
Note that the main problem here is how collections are modeled in terms of OuterJoinableAssociation instances. A "basic collection" results in one OuterJoinableAssociation generated. However, one-to-many and many-to-many collections result in 2 OuterJoinableAssociation instances generated; the first represents the collection itself (mainly the "collection key"), the second represents the associated entity. And in the case of Maps, that could even be 3 OuterJoinableAssociation instances (one for the collection, one for the value, one for the key)!
So another aspect to this will probably be to "link" the OuterJoinableAssociation instances together so that we have a clear understanding of the "isFetched" question for the group.
Longer term, OuterJoinableAssociation should be made to work more like FromElement in the HQL parser code. That is part of the larger "consolidated SQL generation" discussion.