ActionQueue execution order

mynameisflaw · **Joined:** Tue Jun 01, 2010 1:28 pm **Posts:** 1

Hi,

looking at the source code of Hibernate, at org.hibernate.engine.ActionQueue class, my question is:
why the execute actions are in this order: 'insertions', 'updates', 'collectionRemovals', 'collectionUpdates', 'collectionCreations', 'deletions' ?

which problems can occur at database if I move the execution of 'collectionRemovals' and 'deletions' to the top of action list ?

Code:

public void executeActions() throws HibernateException {
      executeActions( collectionRemovals ); // my change
      executeActions( deletions ); // my change
      executeActions( insertions );
      executeActions( updates );
      executeActions( collectionUpdates );
      executeActions( collectionCreations );
   }

VampBoy · **Posted:** Mon Jun 07, 2010 1:48 pm

What are you trying to accomplish with your change? The one thing that springs to mind is a scenario we bump into from time to time where we want to clear a collection and then insert new records into it but then run into unique index violations since the inserts happen prior to the deletes.

If you feel strongly about your use case you might consider raising a JIRA issue as an improvement and see what the devs say. I'm not sure if there's a hard and fast reason to the ordering or not but you could make your change and run their test suite as a starting point to see what comes off the rails.