Author bulb
Recipients Jeremy Banks, Jim.Jewett, Mark.Bucciarelli, Ronny.Pfannschmidt, adamtj, asvetlov, aymeric.augustin, bkircher, bulb, dholth, flox, ghaering, monsanto, pitrou, r.david.murray, scott.urban, torsten, tshepang, zzzeek
Date 2015-08-20.20:36:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
While I agree that the current behaviour is a bug (this bug), and one that renders the package unusable for me (I used apsw or different language instead), I unfortunately have to disagree with Gerhard that the change is not a problem. It can be.

The implicit commit before DDL statements that is gone is not a problem, but the implicit commit *after* them that is *also* gone is. Because if somebody only does DDL statements, and upgrade script might do just that, they will now need a commit.

Scripts that use dbapi2 in a portable way will have the commit, because other databases that support DDL in transactions require it already. But scripts that are only used with current sqlite and possibly mysql (behaviour of which the current version mimics) may not and will break.
Date User Action Args
2015-08-20 20:36:22bulbsetrecipients: + bulb, ghaering, pitrou, Jeremy Banks, r.david.murray, zzzeek, asvetlov, flox, adamtj, dholth, torsten, monsanto, scott.urban, aymeric.augustin, tshepang, Ronny.Pfannschmidt, Mark.Bucciarelli, Jim.Jewett, bkircher
2015-08-20 20:36:22bulbsetmessageid: <>
2015-08-20 20:36:22bulblinkissue10740 messages
2015-08-20 20:36:22bulbcreate