I've found that due to the iterative nature of cascades, in order to get everything working I sometimes needed to drop the "not null" constraint on the children objects so they could handle the parent getting deleted first, then the child. (Otherwise when the parent is deleted, but it hasn't yet cascaded to the child, the child's not-null constraint on the parent reference causes the whole transaction to fail.)

-Dale

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to