← 输入框|bugs.python.org|刷新

➜

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.

作者 james.oldfield
收信人 erlendaasland, ghaering, james.oldfield, lemburg, maggyero, r.david.murray, zzzeek
日期 2021-01-05.11:27:54
SpamBayes Score -1.0
Marked as misclassified 是
Message-id <1609846074.99.0.876112006766.issue39457@roundup.psfhosted.org>
In-reply-to
内容
If this ever gets implemented, "autocommit" would be a terrible name for it. That word has a very specific meaning in SQLite, which is essentially the same as "not in a transaction started with BEGIN ...". At the moment, if you want to explicitly control when transactions start (a good idea considering how confusing the current behaviour is) then you would set isolation_mode to None and manually start a transaction with `execute("BEGIN")` - at which point you are NOT in autocommit mode, until you commit or rollback. According to this proposal, if I want manual control over transactions, I would set `conn.autocommit = True`, even though I *don't* want autocommit mode (according to SQLite's definition)!
历史
日期 用户 动作 参数
2021-01-05 11:27:55james.oldfield修改recipients: + james.oldfield, lemburg, ghaering, r.david.murray, zzzeek, maggyero, erlendaasland
2021-01-05 11:27:54james.oldfield修改messageid: <1609846074.99.0.876112006766.issue39457@roundup.psfhosted.org>
2021-01-05 11:27:54james.oldfield链接issue39457 messages
2021-01-05 11:27:54james.oldfield创建