On Jan 30, 2007, at 5:26 PM, Ian wrote: >> the changed state on your objects is stored in an attribute on the >> object itself called "_state" (and actually, its not the "changes" as >> much as "what was loaded from the database"). you can freely move >> instances from one session to the next (using either save_or_update() >> or merge()) and the changes will be maintained. > > Okay, that doesn't sound so bad. It looks like I would still have to > track deletions myself, but that shouldn't be too much extra work.
if you use cascades to maintain your deletes, i.e. you delete an instance by using the "delete-orphan" cascade and removal from its parent collection, that can also be moved across sessions. I just clarified the description of the "detached" state in the docs on the site. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
