[sqlalchemy] different behavior with schema qualified tables in sqlite since 0.7.x

2011-09-16 Thread Victor Olex
Something's changed with sqlite since 0.6. Once a sqlite engine is created to a physical file the usual workaround for schema change does not work. It works correctly on sqlite in memory and even when reattaching from memory to a file. from sqlalchemy import Column, Sequence, create_engine,

Re: [sqlalchemy] different behavior with schema qualified tables in sqlite since 0.7.x

2011-09-16 Thread Michael Bayer
OK what's changed with SQLite is that file-based databases no longer use a pool - NullPool is used by default.So below, if you want some kind of scope to remain for the life of the Engine you'd need to switch it back to SingletonThreadPool - however, what would be better is to procure a