On 15 Apr 2014, at 1:47pm, MikeD <supp...@dotysoftware.com> wrote: > If another thread deletes/updates or inserts while a SELECT statement is > processing the results could > be unpredictable?
Only if your timing is unpredictable. If you know which command is issued first, you know what the results will be. > Would issuing a BEGIN IMMEDIATE before a SELECT statement > solve this? Not necessary. Even though a SELECT command only reads and database and doesn't change it, SQLite still wraps it in a transaction (BEGIN ... END) for you. Another process trying to modify the database is made to wait until the SELECT is finished. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
