|
||||||||
|
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 |
||||||||
This still exists on Hibernate 4.1.8. Seems like a pretty critical bug. I've been working around it for some time by inserting into the 0th index - but I'm starting to run into correctness issues. I have other code that would like to operate on a correctly ordered list of "B" (child) elements and I'm unable to give it a correctly ordered list due to this bug.
I've been watching
HHH-3332, and a comment pointed me here. Definitely still unresolved.