Igor Tandetnik wrote: > On 7/1/2014 4:55 PM, Clemens Ladisch wrote: >> To prevent deadlocks, transactions that will modify the database should >> be started with BEGIN IMMEDIATE. (This kind of lock is not available >> in shared cache mode.) > > Are you sure?
Sorry, I meant "locking", not "lock". The important thing is that this gets a write lock without holding a read lock first. > If all else fails, one could try and simulate BEGIN IMMEDIATE by running > a dummy modifying statement right after BEGIN - e.g. > > delete from table1 where 0; Would this be atomic? Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
