Re: [sqlalchemy] Migration from 0.5 to 0.9, legacy code and "InvalidRequestError: This transaction is inactive"

2014-09-10 Thread Jonathan Vanasco
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

Re: [sqlalchemy] Migration from 0.5 to 0.9, legacy code and "InvalidRequestError: This transaction is inactive"

2014-09-10 Thread christian . h . m . schramm
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 cr

Re: [sqlalchemy] Migration from 0.5 to 0.9, legacy code and "InvalidRequestError: This transaction is inactive"

2014-09-09 Thread 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 creating/deleting `session` objects and they got recycled. So an error raised on on

Re: [sqlalchemy] Migration from 0.5 to 0.9, legacy code and "InvalidRequestError: This transaction is inactive"

2014-09-09 Thread Michael Bayer
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 an