[sqlalchemy] Re: Temporary Disable Session.mapper with Scoping
On Thu, 15 Nov 2007 10:09:08 -0500, Michael Bayer <[EMAIL PROTECTED]> wrote: > [On Session.mapper] > it would be easier if you just didnt use autosave, id really love to > remove that feature entirely. IMO removing that functionality would make SQLAlchemy a lot more awkward to use. /me votes for keeping it in. -- Gerhard --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sqlalchemy] Re: Temporary Disable Session.mapper with Scoping
Ok, I could do that. On Nov 15, 4:09 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > On Nov 15, 2007, at 9:06 AM, Koen Bok wrote: > > > > > Hi, > > > I use scoped_session in our project for auto object saving which is > > great. But when I initialize a new database I need to flush some > > objects with another engine. I could not find a nice way to do that so > > I created a new session with it's own engine and merged the objects > > into that one and cleared the from my Session object. That worked, but > > all their relations are lost and they have a parent child relation. > > How to do this? > > > Sample code uploaded as test_scope.py > > it would be easier if you just didnt use autosave, id really love to > remove that feature entirely. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sqlalchemy] Re: Temporary Disable Session.mapper with Scoping
On Nov 15, 2007, at 9:06 AM, Koen Bok wrote: > > Hi, > > I use scoped_session in our project for auto object saving which is > great. But when I initialize a new database I need to flush some > objects with another engine. I could not find a nice way to do that so > I created a new session with it's own engine and merged the objects > into that one and cleared the from my Session object. That worked, but > all their relations are lost and they have a parent child relation. > How to do this? > > Sample code uploaded as test_scope.py > it would be easier if you just didnt use autosave, id really love to remove that feature entirely. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
