On Jun 23, 1:08 pm, kris <[EMAIL PROTECTED]> wrote:
>
> Are we setting up the multiple database situation incorrectly for 0.5?
0.4 had an implicit behavior whereby when you hit the lazy loader on
an attribute for an object that was not bound to a session, it would
automatically bind to the current session used by Session.mapper.
This behavior wasn't implemented consistently in all use cases and is
somewhat magic so in 0.5 its removed. So when you do your
Session.close(), you're going to want to transfer all in-memory
objects which you'd like to continue working with to your
scoped_session, using Session.add() or Session.add_all([<unbound
objects>]).
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
