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 erlendaasland, ghaering, james.oldfield, lemburg, maggyero, r.david.murray, zzzeek
Date 2021-01-06.13:21:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1609939316.62.0.16408128795.issue39457@roundup.psfhosted.org>
In-reply-to
Content
I think this issue just discusses the naming of an attribute called ".autocommit".  for the discussion for SQLite's unusual starting of transactions, that's all in two other issues:

https://bugs.python.org/issue9924 

https://bugs.python.org/issue10740

so I would encourage folks to read those discussions.  at issue is the limitation of SQLite that it locks the whole file for transactions, which is the main rationale for why SQLite is hesitant to begin a transaction.  however, without configurability, this means it's not compatible with SAVEPOINT or serializable isolation levels.   when users want to use those two features we have them set isolation_level=None and emit "BEGIN" on the connection directly.    the connection.commit() and connection.rollback() methods continue to be functional
History
Date User Action Args
2021-01-06 13:21:56zzzeeksetrecipients: + zzzeek, lemburg, ghaering, r.david.murray, maggyero, erlendaasland, james.oldfield
2021-01-06 13:21:56zzzeeksetmessageid: <1609939316.62.0.16408128795.issue39457@roundup.psfhosted.org>
2021-01-06 13:21:56zzzeeklinkissue39457 messages
2021-01-06 13:21:56zzzeekcreate