|
||||||||
|
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 |
||||||||
Ok, I uploaded a test. What I'm seeing:
1. cascadeSave of child when parent is saved and parent is not yet in the database: works
2. cascadeSave of child when parent is saved and parent is loaded from the database: fails, no index is inserted
3. save of child (as owning entity): fails, no index is inserted
Regarding 3, I'm not sure if this intentional or not. If it is, it should be documented because it changes the required save behaviour in the relationship by just adding @OrderColumn