Re: [sqlite] COMMIT nested in SELECT returns unexpected results

> Date: Wed, 24 Dec 2014 15:47:41 +0200 > From: RSmith > > In the meantime, could you kindly post the actual connector or SQLite > interface used and which version of it (both the > connector/interface and the SQLite versions) so that we can test fully. We are using sqlite3

Re: [sqlite] COMMIT nested in SELECT returns unexpected results

> On 24 Dec 2014, at 10:50am, Jim Carroll wrote: > > #!/usr/bin/env python > import sqlite3 as sq Sorry, I may have just realised what's wrong. You are misusing your python library. See the documentation at You cannot

Re: [sqlite] COMMIT nested in SELECT returns unexpected results

On 2014/12/24 12:50, Jim Carroll wrote: I understand that performing a SELECT and nested COMMIT on the same table is not supported in sqlite, but I would have expected a COMMIT on a separate table would not be a problem. Some test code in python however reveals that performing the COMMIT

Re: [sqlite] COMMIT nested in SELECT returns unexpected results

On 24 Dec 2014, at 10:50am, Jim Carroll wrote: > I understand that performing a SELECT and nested COMMIT on the same table is > not supported in sqlite, but I would have expected a COMMIT on a separate > table would not be a problem. Some test code in python however reveals

[sqlite] COMMIT nested in SELECT returns unexpected results

I understand that performing a SELECT and nested COMMIT on the same table is not supported in sqlite, but I would have expected a COMMIT on a separate table would not be a problem. Some test code in python however reveals that performing the COMMIT disrupts the SELECT statement, and causes