[hibernate-dev] Question about current flush ordering

[Vlad Mihalcea]

Hi,

There is this issue that has puzzled me for many years related to
ActionQueue ordering:

- OrphanRemovalAction.class,
- AbstractEntityInsertAction.class,
- EntityUpdateAction.class,
- QueuedOperationCollectionAction.class,
- CollectionRemoveAction.class,
- CollectionUpdateAction.class,
- CollectionRecreateAction.class,
- EntityDeleteAction.class,
Why is it that we execute the OrphanRemovalAction firsts, but the
EntityDeleteAction last?

Shouldn't the EntityDeleteAction be executed before Insert or Update?

There musts be a reason for choosing this ordering, but I can't figure out
why the EntityDeleteAction was chosen to be executed last.

Vlad