Ah, so it seems I was most confused about the intended usage of the scoped session - I was assuming that because it was designed to be multithreaded, that would imply that the same instance would be used for more than one request ... because an individual request is typically handled by a single thread. Thanks for the clarification, I'll implement the change in the code.
I appreciate your software by the way, thanks for writing some fantastic code. BTW, I was using sqlite in a development environment. I'm using postgres in production :) For anyone else reading, using the NullPool was a hack around a bug in the database driver for sqlite, which may no longer be necessary. On Mar 8, 7:47 pm, Michael Bayer <mike...@zzzcomputing.com> wrote: > On Mar 8, 2012, at 4:34 PM, Chris Withers wrote: > > > > >> avoid doing that. I'm using a "NullPool" connection to the database > >> engine, by the way, just in case that would change anything. > > > Why would you do that? > > I advise using NullPool with SQLite in the docs, if you use SQLA 0.7 the > SQLite dialect chooses NullPool by default. > > > > >> SQlite3 database backend > > > Why would you do that? ;-) > > thats the DBAPI that SQLAlchemy uses with sqlite.... -- 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 sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
