If another thread deletes/updates or inserts while a SELECT statement is processing the results could be unpredictable? Would issuing a BEGIN IMMEDIATE before a SELECT statement solve this?
-- View this message in context: http://sqlite.1065341.n5.nabble.com/TRANSACTIONs-tp23854p75089.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
