> del p.children[3]
basically cascade has nothing to say about this operation when applied to transient instances. the history tracking will not see the item as ever being part of the "children" collection since you added it then removed it without flushing. also, the "delete" cascade operation does not remove the item from the session, it only marks the item to be deleted from the DB, which after a flush results in the item being removed from the session. but this item cant be deleted since it was never persisted. SA basically knows nothing about the instance's relationships to anything else and would rather not guess what you'd like to do with it. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
