[sqlalchemy] Re: Many to many and orphan deletion

2008-01-10 Thread Laurent Houdard
> how about, go into sessionextension.after_flush(), make a new session > local to the operation, issue a Query with the Select for all orphan > keywords, delete them all and flush that sub-session, then expunge() > those keywords from the parent session sent to after_flush, like this: > [...] Br

[sqlalchemy] Re: Many to many and orphan deletion

2008-01-10 Thread Laurent Houdard
On Jan 10, 4:00 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > A statement issued in SessionExtension would fire unconditionally upon > any flush(), so thats the trigger there. not sure what you mean by > "track" here, if it means you want to know the keywords that were > deleted, you'd just iss

[sqlalchemy] Re: Many to many and orphan deletion

2008-01-10 Thread Laurent Houdard
On Jan 9, 9:24 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > So if I understand what youre looking to do here, youd like a keyword > to be deleted when the last parent is removed ? That is exactly what I would like... > if youd like to check for this condition after each flush you can do > i

[sqlalchemy] Re: Many to many and orphan deletion

2008-01-09 Thread Laurent Houdard
> Can anybody help me ? ...No one ?? --~--~-~--~~~---~--~~ 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

[sqlalchemy] Many to many and orphan deletion

2008-01-04 Thread Laurent Houdard
I have nodes with a self-referential parent-child one-to-many relation, and a many-to-many relation between nodes and keywords. I would like to manage orphan keywords. It doesn't work with cascade=delete-orphan which is not adapted to many-to-many relations. I could do it manually, but I can't fi