[issue9924] sqlite3 SELECT does not BEGIN a transaction, but should according to spec
report at bugs.python.org
Thu Sep 23 06:02:37 CEST 2010
mike bayer <mike_mp at zzzcomputing.com> added the comment:
My own comment here is that I'm supposing the "late BEGIN" behavior is to cut down on SQLite's file locking. I think a way to maintain that convenience for most cases, while allowing the stricter behavior that makes SERIALIZABLE isolation worthwhile, would be an option to sqlite3.connect() that moves the implicit BEGIN to before any DQL, not just DML, statement.
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list