Am Dienstag, 9. September 2014 18:12:26 UTC+2 schrieb Jonathan Vanasco:
What do you see if you drop SqlAlchemy's logging to DEBUG?
I think I had a similar problem a long time ago, migrating from 0.5 to
0.8. In my case, the issue was with the `Session` factory -- i was not
properly
unfortunately I can't recall... I encountered this a long time ago (2010 or
so), so I think it was a migration from .5 to .6x
what i do remember, is that once I figured out how wrong i was about
setting up the session... i was amazed that anything worked.
I looked at the .5x and .6x changelogs
Hello everyone,
I am currently in the process of migrating a large legacy code base I
inherited from SQLAlchemy 0.5 to 0.9. There is a somewhat confusing stack
of custom decorator magic for connection, session and transaction handling
– too unwieldy to post here in its entirety, but very
On Sep 9, 2014, at 3:30 AM, christian.h.m.schr...@googlemail.com wrote:
Hello everyone,
I am currently in the process of migrating a large legacy code base I
inherited from SQLAlchemy 0.5 to 0.9. There is a somewhat confusing stack of
custom decorator magic for connection, session and
What do you see if you drop SqlAlchemy's logging to DEBUG?
I think I had a similar problem a long time ago, migrating from 0.5 to 0.8.
In my case, the issue was with the `Session` factory -- i was not properly
creating/deleting `session` objects and they got recycled. So an error
raised on
