The difference is that insert ordering is merely a question of performance
in order to better leverage JDBC batching. Here you are suggesting that
there is a bug in the order of deletes. Or are you just wanting to order
the deletes to better leverage JDBC batching as well? It's not clear.
On Wed, Mar 25, 2015 at 5:05 PM, Mihalcea Vlad <mih_vlad(a)yahoo.com> wrote:
While INSERT sorting is handled by ActionQueue.InsertActionSorter, DELETE
statements are not sorted at all.
A DeleteActionSorter woudl have to rearrange DELETES in the opposite order
as the INSERT sorting, the Children having to be deleted first.
The current work-around is to dissociate all Children and manually flush
the Session, so that the orphan-removal kicks in before the Parent entities
Any plans for supporting such a feature?