[OPENJPA-817] Order of inserts lost when using ConstraintUpdateManager

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.1.0, 1.2.0, 1.2.1, 1.3.0, 2.0.0-M2
• Fix Version/s: 1.2.0, 1.2.1, 1.3.0, 2.0.0-M2
• Component/s: jdbc
• Assignee: Michael Dick
• Reporter: Michael Dick
• Due: 09/Dec/08
• Created: 05/Dec/08 20:21
• Updated: 21/Sep/16 14:21
• Resolved: 09/Dec/08 18:56

Description

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.

Issue Links

• is depended upon by: OPENJPA-1092 enable test case for jpql