[issue10740] sqlite3 module breaks transactions and potentially corrupts data

2016-03-23 Thread Rian Hunter
Changes by Rian Hunter <r...@thelig.ht>: -- nosy: -rhunter ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10740> ___ __

[issue10740] sqlite3 module breaks transactions and potentially corrupts data

2016-03-23 Thread Rian Hunter
Changes by Rian Hunter <r...@thelig.ht>: Added file: http://bugs.python.org/file42250/test_sqlite.py ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

[issue10740] sqlite3 module breaks transactions and potentially corrupts data

2016-03-23 Thread Rian Hunter
Changes by Rian Hunter <r...@thelig.ht>: Removed file: http://bugs.python.org/file42249/test_sqlite.py ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

[issue10740] sqlite3 module breaks transactions and potentially corrupts data

2016-03-23 Thread Rian Hunter
Changes by Rian Hunter <r...@thelig.ht>: Added file: http://bugs.python.org/file42251/test_sqlite.py ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

[issue10740] sqlite3 module breaks transactions and potentially corrupts data

2016-03-23 Thread Rian Hunter
Changes by Rian Hunter <r...@thelig.ht>: Removed file: http://bugs.python.org/file42250/test_sqlite.py ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

[issue10740] sqlite3 module breaks transactions and potentially corrupts data

2016-03-22 Thread Rian Hunter
Rian Hunter added the comment: Implicit transactions can also cause mysterious "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 attach

[issue10740] sqlite3 module breaks transactions and potentially corrupts data

2016-03-23 Thread Rian Hunter
Rian Hunter added the comment: @mike Yes you're right, This bug report is different, my mistake. DB-API may require implicit transactions but pysqlite should open a transaction before *any* non-DDL statement, including "SELECT", not just DML statements. Currently one must issue a

[issue26625] SELECT-initiated transactions can cause "database is locked" in sqlite

2016-03-23 Thread Rian Hunter
New submission from Rian Hunter: 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 s

[issue26625] SELECT-initiated transactions can cause "database is locked" in sqlite

2016-03-23 Thread Rian Hunter
Rian Hunter added the comment: duplicate of #9924 -- resolution: -> duplicate status: open -> closed ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

[issue9924] sqlite3 SELECT does not BEGIN a transaction, but should according to spec

2016-03-23 Thread Rian Hunter
Changes by Rian Hunter <r...@thelig.ht>: -- versions: +Python 3.2, Python 3.5, Python 3.6 ___ Python tracker <rep...@bugs.python.org> <http://bugs.pytho

[issue9924] sqlite3 SELECT does not BEGIN a transaction, but should according to spec

2016-03-23 Thread Rian Hunter
Rian Hunter added the comment: 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").