Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315138 - Incorrect Commit Order Calculation
Summary: Incorrect Commit Order Calculation
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-31 16:22 EDT by Gordon Yorke CLA
Modified: 2022-06-09 10:10 EDT (History)
2 users (show)

See Also:

Attachments
Potential Patch (7.72 KB, patch)
2010-06-09 14:54 EDT, Gordon Yorke CLA 		no flags Details | Diff
Recreation of problem (5.88 KB, application/octet-stream)
2010-11-18 11:15 EST, Tom Ware CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gordon Yorke CLA 2010-05-31 16:22:46 EDT 
A node in the commit order calculation is only visited once.  Should a descriptor be referenced by multiple Classes it may not have it's commit order updated in relation to the second reference resulting in incorrect commit order for some of the objects resulting in failed deletes.
Comment 1 Gordon Yorke CLA 2010-06-09 14:54:40 EDT 
Created attachment 171570 [details]
Potential Patch

The attachment contains proposed updates to improve the commit order calculation
Comment 2 Tom Ware CLA 2010-11-18 10:47:28 EST 
I have been unable to recreate this issue in a way that does not also depend on a solution for bug 330580.  Please post a recreation if you can think of one.  I will attach the object model I have that comes the closest.
Comment 3 Tom Ware CLA 2010-11-18 11:15:30 EST 
Created attachment 183395 [details]
Recreation of problem

Attaching a zip file that recreates the problem.  To fix the issue, for this recreation in a general way, the fixes for bug 330580 and bug 315141 will be reqquired.

To run the recreation, import the project into an Eclipse workspace that contains the EclipseLInk development Eclipse projects and alter the persistence.xml to point at your DB.
Comment 4 Tom Ware CLA 2010-11-18 11:16:38 EST 
FYI: recreation has been attached for informational purposes only, a recreation of this issue that does show other issues as well is still required.
Comment 5 Eclipse Webmaster CLA 2022-06-09 10:10:09 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink