Message 175946 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	strcat
Recipients	docs@python, strcat
Date	2012-11-19.07:40:50
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1353310851.97.0.745365364193.issue16509@psf.upfronthosting.co.za>
In-reply-to

Content
The sqlite3 documentation now includes a Multithreading section explaining issues with older sqlite versions, but still doesn't directly cover disabling check_same_thread beyond listing it as a possible parameter. As far as I can tell, reusing sqlite connections in different threads (such as from a pool) is safe, as long as no attempt is made to use them from multiple threads with no locking.

The sqlite3 documentation now includes a Multithreading section explaining issues with older sqlite versions, but still doesn't directly cover disabling check_same_thread beyond listing it as a possible parameter.

As far as I can tell, reusing sqlite connections in different threads (such as from a pool) is safe, as long as no attempt is made to use them from multiple threads with no locking.

History
Date	User	Action	Args
2012-11-19 07:40:52	strcat	set	recipients: + strcat, docs@python
2012-11-19 07:40:51	strcat	set	messageid: <1353310851.97.0.745365364193.issue16509@psf.upfronthosting.co.za>
2012-11-19 07:40:51	strcat	link	issue16509 messages
2012-11-19 07:40:50	strcat	create