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 disrupts the SELECT statement, and causes duplicate
data to be returned.
If this is not a supported operation, would you mind pointing me to the docs
so I can understand it better?
The example code works fine if executed in another language (in C first, then I tried PHP since it's also scripting, but I don't
have Python on Linux to try with). That said, I use explicit Transactions, your interface seems to do some form of automatic
transaction (I only see commits, no begins...) which might be a clue.
i.e. this is not an SQLite problem per se, unless your version has a problem. I am expecting it might be a peculiarity with the
connector you are using. Would that be PySQLite? If so, the devs for that also see this list so maybe they could comment. I can't
imagine a scenario in which your posted results would be the expected result though, so you are correct to question it.
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.
You can get the version of SQLite returned with this query:
*select sqlite_version();*
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
