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 r.david.murray
Recipients Jeremy Banks, Jim.Jewett, Mark.Bucciarelli, Ronny.Pfannschmidt, adamtj, asvetlov, aymeric.augustin, bulb, dholth, flox, ghaering, monsanto, pitrou, r.david.murray, scott.urban, torsten, tshepang, zzzeek
Date 2014-06-14.14:23:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402755800.75.0.667202814587.issue10740@psf.upfronthosting.co.za>
In-reply-to
Content
> My take is to avoid the problem entirely, and not inflict it to new users, by providing an option to start in autocommit mode and then create transactions only when you want them.

If this statement is accurate, the what you are proposing is just a different (presumably clearer) spelling for 'isolation_level = None'?

I also don't understand why we don't just fix the screwy behavior with regards to savepoint.  It's hard to see how fixing that could be a backward compatibility problem (in a feature release), since you can't use savepoints without isolation_level=None as it stands now.
History
Date User Action Args
2014-06-14 14:23:20r.david.murraysetrecipients: + r.david.murray, ghaering, pitrou, Jeremy Banks, zzzeek, asvetlov, flox, adamtj, dholth, torsten, monsanto, scott.urban, aymeric.augustin, tshepang, Ronny.Pfannschmidt, Mark.Bucciarelli, Jim.Jewett, bulb
2014-06-14 14:23:20r.david.murraysetmessageid: <1402755800.75.0.667202814587.issue10740@psf.upfronthosting.co.za>
2014-06-14 14:23:20r.david.murraylinkissue10740 messages
2014-06-14 14:23:20r.david.murraycreate