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.
Thanks in advance. Jonathan Trahair _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
