Affects Version/s: 1.0.0
Fix Version/s: None
When creating a joined subclass relationship, it is desirable on the database side to place an integrity constraint on the subclass table that its object_id must exist in the parent class's table. (Because the subclass's row cannot exist without the parent class's row.)
Unfortunately, OpenJPA orders the inserts in the opposite direction, trying to insert the child entity first (probably because that's the entity that the code is actually persisting), so with the integrity constraint in place, the insert will fail.
It would be nice if in a joined-subclass relationship where multiple inserts were needed, SQL would be issued in order of highest in the class hierarchy to lowest so that integrity constraints on the database won't be violated.
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Resolution||Invalid [ 6 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|2d 4h 45m||1||Patrick Linskey||06/Nov/07 06:41|