Is there a way to specify the order of inserts/updates/deletes used for saving changes across multiple BO's?



Suppose I have multiple tables (Parent, Child, Grandchild) with database-side FK constraints. I might want inserts to be handled top-down (Parent->Child->Grandchild) and deletes bottom-up (Grandchild ->Child->Parent) in order not to violate the FK constraints.



What's the best way to handle this in the general case?