Is there a way to enforce delete order. I have an evolved application that applies many controls to a set of recieved files. Late in the development I have a Use Case that states that I should delete everything the user has done. This is "easy"...just delete the parent object. But as it turns out this implies deleting many object and complex hierrarchies. In one case I found NH trying to delete thing that conflicts with a foreign key constraint.

Is there a way to control the delete order, or I'm better off with a Stored procedure for this?? Maybe I'm missing something, like a not-null or something to tell nhibernate how to follow the cascade order and which entities deletes first.

Thanks!