Order of inserts lost when using ConstraintUpdateManager
--------------------------------------------------------
Key: OPENJPA-817
URL: https://issues.apache.org/jira/browse/OPENJPA-817
Project: OpenJPA
Issue Type: Improvement
Components: jdbc
Affects Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.1.0, 1.1.1, 1.2.0, 1.2.1, 1.3.0,
2.0.0
Reporter: Michael Dick
Assignee: Michael Dick
Fix For: 1.2.1, 1.3.0, 2.0.0
The ConstraintUpdateManager does a good job of ordering inserts, updates and deletes when
the internal metadata is complete. If the internal metadata is not complete (ie there are
no @ForeignKey annotations) SQL statements are executed in an arbitrary order.
The application can avoid this by adding the appropriate annotations, or by obtaining the
data from the database, but we can make some attempt to preserve the order of execution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|