Eclipse Community Forums: EclipseLink » Forcing a different operations order on persited entity

Help

Home

Home » Eclipse Projects » EclipseLink » Forcing a different operations order on persited entity

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

Forcing a different operations order on persited entity [message #1742949]

Thu, 08 September 2016 18:56

test test

Messages: 1
Registered: September 2016

Junior Member

I have an already persisted entity with EclipseLink. I perform some changes on it that cause a constraint violation because of the inserting before updating.

As stated in the documentation the operations are performed in the following order Insert/Update/Delete. There is a method that permits for the delete to be executed first but I can't find any solution to make an update execute before insert. Is there some workaround so I could maybe redefine the order like Delete/Update/Insert?

Report message to a moderator

Re: Forcing a different operations order on persited entity [message #1743797 is a reply to message #1742949]

Mon, 19 September 2016 16:27

Chris Delahunt

Messages: 1389
Registered: July 2009

Senior Member

Why would inserting before the update cause a constraint violation? Generally something has to exist in the database before any existing rows can be updated to reference them, so the insert/update order is one that is calculated on an entity by entity basis. If there is a constraint being hit, is it something that you have mapped in your entity, or is it due to a circular mapping?

Report message to a moderator

Previous Topic:	Exception Description: No conversion value provided for the value
Next Topic:	JPA - orphanRemoval in embedded entity not working

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Apr 24 22:01:10 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter