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

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

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 and

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

[sqlalchemy] Choosing pattern for vertical table like mapping.

2014-09-09 Thread Anton
Hi, I need some help choosing the right pattern for the models I have. I have the following tables: Entity (INT id, VARCHAR name) Group (INT id, VARCHAT name) GroupEntityAttributes(INT entity_id, INT group_id, VARCHAR key, VARCHAR name) Entity and Group models are pretty straight forward. But

[sqlalchemy] Re: Choosing pattern for vertical table like mapping.

2014-09-09 Thread Anton
Trying to use with multiple table mapping. On Tuesday, September 9, 2014 1:03:25 PM UTC-7, Anton wrote: Hi, I need some help choosing the right pattern for the models I have. I have the following tables: Entity (INT id, VARCHAR name) Group (INT id, VARCHAT name)

Re: [sqlalchemy] too many SQL variables in in_

2014-09-09 Thread pyArchInit ArcheoImagineers
Hi Michael and thanks a lot. Il giorno venerdì 5 settembre 2014 18:23:31 UTC+2, Michael Bayer ha scritto: you batch out the values to be used in the IN, then one of two choices: my preference is to run separate SELECT statements, using IN with each batch. If you really can’t do that, you

Re: [sqlalchemy] too many SQL variables in in_

2014-09-09 Thread Michael Bayer
On Sep 9, 2014, at 4:45 PM, pyArchInit ArcheoImagineers pyarchi...@gmail.com wrote: Hi Michael and thanks a lot. Il giorno venerdì 5 settembre 2014 18:23:31 UTC+2, Michael Bayer ha scritto: you batch out the values to be used in the IN, then one of two choices: my preference is to run

Re: [sqlalchemy] too many SQL variables in in_

2014-09-09 Thread pyArchInit ArcheoImagineers
Hi Michael, I use my method for every tables of my DB so I pass the mapper class, the name of id, etc, etc. and through a string I build the cmd to pass to the eval function. I'll try your method.. Thanks a lot. Best regards Luca Il giorno martedì 9 settembre 2014 22:58:59 UTC+2, Michael

[sqlalchemy] Alembic 0.6.7 Released

2014-09-09 Thread Michael Bayer
Alembic 0.6.7 is now available. This is a very small release with two fixes that were ready to go out, and after which I'm going to start on the 0.7.0 series. The two changes are support for SQL Server sp_rename() for tables, and some workarounds to allow Postgresql functional indexes to be