On 17 April 2013 14:39, J Trahair <[email protected]> wrote: > Hi everyone > > Can my application lock the database for its own exclusive use at the > beginning of a series of INSERTs UPDATEs and SELECTs, then unlock it again > afterwards? I've read about the five locking states (unlocked, shared, etc.) > but I assume the dll handles all that at INSERT or UPDATE time. I'm looking > for a way to ensure other users aren't allowed to write to the database > during this quarter-second period.
http://www.sqlite.org/lang_transaction.html BEGIN EXCLUSIVE > > Thanks in advance. > > Jonathan Trahair Regards, Simon _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
