Don't forget that your "other" applications will need to extend their connection time outs, otherwise, while "this" application has the lock, the "other" applications will time out and throw errors.
On Wed, Apr 17, 2013 at 9:43 AM, Simon Davies <simon.james.dav...@gmail.com>wrote: > On 17 April 2013 14:39, J Trahair <j.trah...@foreversoftware.co.uk> 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 > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
