Eclipse Community Forums: EclipseLink » Private Ownership and Unique Constraints

Help

Home

Home » Eclipse Projects » EclipseLink » Private Ownership and Unique Constraints

Show: Today's Messages :: Show Polls :: Message Navigator

Private Ownership and Unique Constraints [message #521543]

Thu, 18 March 2010 00:21

Daniel Frank

Messages: 6
Registered: March 2010

Junior Member

Dears,

I have a problem using @PrivateOwned (or the new orphanRemoval) because the framework insert before remove
the orphans.
There is a way to change the order?
Thanks in advance,

Report message to a moderator

Re: Private Ownership and Unique Constraints [message #521663 is a reply to message #521543]

Thu, 18 March 2010 12:46

Chris Delahunt

Messages: 1389
Registered: July 2009

Senior Member

Hello,

Native EclipseLink API has a flag that can be used to process deletes first, but I do not believe it will help with privately owned relationships, as they are deleted as they are found in the update/insert stage. Can you describe the problem you are having a bit more and what you are trying to do and someone might be able to come up with a fix or workaround.

Best Regards,
Chris

Report message to a moderator

Re: Private Ownership and Unique Constraints [message #521674 is a reply to message #521543]

Thu, 18 March 2010 13:23

Daniel Frank

Messages: 6
Registered: March 2010

Junior Member

Hello,
Look this scenario, i have a entity Contact with a list of Telephone entity(id, number, type) and number has a unique key. If i remove a telephone (e.g number=0000, type=mobile) and add other telephone (number=0000, type=personal), i will have a unique constraint violation when i persist the contact, because eclipselink will add new telephone before remove the oldest.

Report message to a moderator