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 malin
Recipients berker.peksag, erlendaasland, lemburg, malin, serhiy.storchaka
Date 2021-12-06.03:51:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1638762711.81.0.938440705838.issue44092@roundup.psfhosted.org>
In-reply-to
Content
I think this change is no problem.
Erlend E. Aasland's explanation is very clear. 

There is only one situation that a problem may occur. Write code with SQLite 3.8.7.2+ (2014-11-18), and run it on 3.7.15 (2012-12-12) ~ 3.8.7.1-, but this situation may be difficult to happen, we can note this situation in doc.

More securely, if run on SQLite 3.8.7.1-, and encounter SQLITE_ABORT_ROLLBACK error code, a prompt can be given to explain the reason.

Also note that the current main branch is buggy. If don't adopt this change or revert this change later, don't forget to fix the bug of msg407185 (`pysqlite_Statement.in_use` flag is not reset).
History
Date User Action Args
2021-12-06 03:51:51malinsetrecipients: + malin, lemburg, berker.peksag, serhiy.storchaka, erlendaasland
2021-12-06 03:51:51malinsetmessageid: <1638762711.81.0.938440705838.issue44092@roundup.psfhosted.org>
2021-12-06 03:51:51malinlinkissue44092 messages
2021-12-06 03:51:51malincreate