Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » Forcing a different operations order on persited entity
Forcing a different operations order on persited entity [message #1742949] Thu, 08 September 2016 18:56 Go to next message
test test is currently offline test testFriend
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?
Re: Forcing a different operations order on persited entity [message #1743797 is a reply to message #1742949] Mon, 19 September 2016 16:27 Go to previous message
Chris Delahunt is currently offline Chris DelahuntFriend
Messages: 1275
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?
Previous Topic:Eclipse link 2.5 + weblogic 12.1.3 memory issue with DMS
Next Topic:EclipseLink 2.7.0 Roadmap
Goto Forum:
  


Current Time: Mon Dec 11 23:00:33 GMT 2017

Powered by FUDForum. Page generated in 0.01739 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software