➜

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 rhunter
Recipients dholth, ghaering, rhunter, rnortman, zzzeek
Date 2016-03-23.16:38:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1458751131.34.0.643551687672.issue9924@psf.upfronthosting.co.za>
In-reply-to
Content 
This bug can also lead to subtle and unintuitive "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"). I've attached code that demonstrates this issue.

I disagree that the current behavior cuts down on SQLite file locking. As soon as any SELECT statement is opened, an implicit lock is held by SQLite (whether it resides within a BEGIN block or not): https://www.sqlite.org/lockingv3.html

SQLite has been designed to do its own "late locking." Pysqlite does not need to duplicate this behavior.

This is a clear-as-day bug and should be fixed.
History
Date User Action Args
2016-03-23 16:38:51rhuntersetrecipients: + rhunter, ghaering, rnortman, zzzeek, dholth
2016-03-23 16:38:51rhuntersetmessageid: <1458751131.34.0.643551687672.issue9924@psf.upfronthosting.co.za>
2016-03-23 16:38:51rhunterlinkissue9924 messages
2016-03-23 16:38:51rhuntercreate