Closed
Description
Migrated issue, originally created by Michael Bayer (@zzzeek)
it shouldn't be too hard these days to just switch off of a ":memory:" connection or not and just use NullPool for file-based connections. Its a little dated for us to still be doing threadlocal-by-default here.
Attachments: sqlite_nullpool.patch
Metadata
Metadata
Assignees
Type
Projects
Relationships
Development
No branches or pull requests
Participants
Activity
sqlalchemy-bot commentedon Sep 19, 2010
Michael Bayer (@zzzeek) wrote:
attached patch is complete. Also removes the usage of "threadlocal" pool with the "threadlocal" engine strategy (not really needed).
sqlalchemy-bot commentedon Nov 18, 2010
Michael Bayer (@zzzeek) wrote:
put a note in the SQLite docs also about the "pool_threadlocal" flag, which will help a lot of folks with locking in a single thread.
sqlalchemy-bot commentedon Dec 8, 2010
Michael Bayer (@zzzeek) wrote:
61840ab
sqlalchemy-bot commentedon Dec 8, 2010
Changes by Michael Bayer (@zzzeek):