Author jamercee
Recipients jamercee, r.david.murray
Date 2014-12-29.22:29:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <00a401d023b6$e3438f20$a9caad60$@carroll.com>
In-reply-to <1419876492.9.0.253732586674.issue23129@psf.upfronthosting.co.za>
Content
Hi David,

One more data point. Although I demonstrated the bug using the .execute() 
method associated with a connection object -- you can also create the exact 
problem using the .execute() method associated with cursors. This leaves no 
means to COMMIT inside a nested SELECT.

The members of the sqlite mailing list confirmed they had no problem executing 
the SQL statements using C and PHP. I think this is a bug, rather than just a 
problem with the docs.

I've been digging around the pysqlite C source but can't quite figure out 
what's going on yet.

Jim

> -----Original Message-----
> From: R. David Murray [mailto:report@bugs.python.org]
> Sent: Monday, December 29, 2014 1:08 PM
> To: jim@carroll.com
> Subject: [issue23129] sqlite3 COMMIT nested in SELECT returns
> unexpected results
>
>
> R. David Murray added the comment:
>
> 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.
>
> ----------
> nosy: +r.david.murray
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue23129>
> _______________________________________
History
Date User Action Args
2014-12-29 22:29:33jamerceesetrecipients: + jamercee, r.david.murray
2014-12-29 22:29:33jamerceelinkissue23129 messages
2014-12-29 22:29:33jamerceecreate