➜

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 rhunter
Recipients Jeremy Banks, Jim.Jewett, Mark.Bucciarelli, Ronny.Pfannschmidt, adamtj, asvetlov, aymeric.augustin, bkircher, bulb, dholth, flox, ghaering, monsanto, pitrou, r.david.murray, rhunter, scott.urban, torsten, tshepang, zzzeek
Date 2016-03-23.16:19:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1458749986.08.0.214085516233.issue10740@psf.upfronthosting.co.za>
In-reply-to
Content 
@mike Yes you're right, This bug report is different, my mistake.

DB-API may require implicit transactions but pysqlite should open a transaction before *any* non-DDL statement, including "SELECT", not just DML statements. Currently one must issue a dummy DML statement just to open a transaction that otherwise would start with a SELECT statement.

I see nothing in DB-API (https://www.python.org/dev/peps/pep-0249/) that says transactions should implicitly open before DML statements and not SELECT statements.
History
Date User Action Args
2016-03-23 16:19:46rhuntersetrecipients: + rhunter, 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, bulb, bkircher
2016-03-23 16:19:46rhuntersetmessageid: <1458749986.08.0.214085516233.issue10740@psf.upfronthosting.co.za>
2016-03-23 16:19:46rhunterlinkissue10740 messages
2016-03-23 16:19:45rhuntercreate