On Sep 9, 2007, at 5:09 AM, Jean-Philippe Dutreve wrote:
> > Another solution could be to inverse the order: > - first delete the parent (so the rule RESTRICT is immediately fired) > - second set null the FKs. hm, except that "RESTRICT" is the same as the default of "NO ACTION". The feature is added in r3486, checkout from the trunk. Specify passive_deletes='all' to your relation(), do not set "delete" or "delete-orphan" cascade. No nulling out of the child columns will occur when the parent is deleted. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
