Hi, 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 delete occurs. Any plans for supporting such a feature? Vlad Mihalcea