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 jamercee, r.david.murray
Date 2014-12-29.18:08:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1419876492.9.0.253732586674.issue23129@psf.upfronthosting.co.za>
In-reply-to
Content
I'd say you have a bug here of some sort, but I'm not sure if it is a doc bug or a code bug.  Commit specifically does *not* reset the cursors, according to the code, but I'm not even sure what resetting a cursor means :)  I've poked around the sqlite3 module's code a bit, but not enough to have an answer to this.  I do note that a commit does a call to sqlite3_reset on all statements associated with the connection, and I suspect that's where the problem originates.  Which probably makes it a doc bug.
History
Date User Action Args
2014-12-29 18:08:13r.david.murraysetrecipients: + r.david.murray, jamercee
2014-12-29 18:08:12r.david.murraysetmessageid: <1419876492.9.0.253732586674.issue23129@psf.upfronthosting.co.za>
2014-12-29 18:08:12r.david.murraylinkissue23129 messages
2014-12-29 18:08:12r.david.murraycreate