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 zzzeek
Recipients zzzeek
Date 2010-09-23.04:02:36
SpamBayes Score 0.0012181584
Marked as misclassified No
Message-id <1285214557.72.0.599610833317.issue9924@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2010-09-23 04:02:37zzzeeksetrecipients: + zzzeek
2010-09-23 04:02:37zzzeeksetmessageid: <1285214557.72.0.599610833317.issue9924@psf.upfronthosting.co.za>
2010-09-23 04:02:36zzzeeklinkissue9924 messages
2010-09-23 04:02:36zzzeekcreate