Author rhunter
Recipients rhunter
Date 2016-03-23.16:28:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1458750514.03.0.475841204409.issue26625@psf.upfronthosting.co.za>
In-reply-to
Content
When a transaction starts with a SELECT statement this can invoke a "database is locked" error if the SELECT statement is not exhausted or explicitly closed.

This can lead to subtle "database is locked" bugs, even when a large timeout is set on the connection. Many, many people are affected by this bug (search the web for "python sqlite database is locked").

The attached code demonstrates this bug and possible (unintuitive) fixes. The best workaround is to "explicitly" start a transaction in these cases by issuing a dummy DML statement. This seems very clumsy.

My proposed fix is to implicitly open a transaction before all non-DDL statements (including SELECT statements), not just DML statements.

If there won't be a fix soon, then at least the documentation should note this quirky behavior.
History
Date User Action Args
2016-03-23 16:28:34rhuntersetrecipients: + rhunter
2016-03-23 16:28:34rhuntersetmessageid: <1458750514.03.0.475841204409.issue26625@psf.upfronthosting.co.za>
2016-03-23 16:28:34rhunterlinkissue26625 messages
2016-03-23 16:28:33rhuntercreate