that is a thing of beauty. Thanks, Mike On Feb 6, 2008 12:24 PM, Michael Bayer <[EMAIL PROTECTED]> wrote:
> > > On Feb 6, 2008, at 12:20 PM, Rick Morrison wrote: > > > Is a session required for any form of object state tracking, or is > > it all done on the mapped objects? > > > > What I'd like to do is to load a graph of related objects, and keep > > them around for a number of change requests. It's a web app, so the > > session will be going away between requests. > > > > There's going to be a parent object and a tree of child objects. > > Processing requests will entail all three types of state change on > > the objects, adding new items to mapped collections, removing > > objects from mapped collections, and modifying the parent objects > > and various child objects. > > > > Between requests, what I'd like to do is either just cache the > > parent object or pickle it to temp storage, modifying it on request. > > There will be a final "checkout" op that will commit all the changes > > in one shot. > > > > So (finally), the question: Can I just save the pickled object > > itself, or do I need to somehow keep a session along with it? I'm > > pretty sure that add + updates are tracked on the objects, but I'm > > not sure about deletes..... > > > state tracking is all inside of instance._state and is completely > independent of Session. it also entirely pickles/unpickles along with > the instance. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
