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, ghaering, malin, palaviv, serhiy.storchaka
Date 2017-01-26.03:58:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1485403087.75.0.666545510846.issue29121@psf.upfronthosting.co.za>
In-reply-to
Content
After read some issues, there are two major concerns:
1, backward compatibility.
2, implicit commit is bad, tolerates bug-prone codes.

However they are not contradictory if we print a warning when doing an implicit commit. Some messages like this:
    Warning: sqlite3 module issued an implicit commit before executing VACUUM, you should commit this transaction by yourself, that's a good habit, etc..

Then we can keep backward compatibility, and no longer commit implicitly.
History
Date User Action Args
2017-01-26 03:58:07malinsetrecipients: + malin, ghaering, berker.peksag, serhiy.storchaka, palaviv
2017-01-26 03:58:07malinsetmessageid: <1485403087.75.0.666545510846.issue29121@psf.upfronthosting.co.za>
2017-01-26 03:58:07malinlinkissue29121 messages
2017-01-26 03:58:07malincreate