Information on how to open SQLite files: http://www.sqlite.org/c3ref/open.html How the locking mechanisms work: http://sqlite.org/lockingv3.html
Specifically, it'll depend on the language or wrapper you're using to access the database. In my case (Delphi) there is an option in the open function that will allow me to specify exactly HOW I want to open a file. If you use an exclusive lock, no other application will be able to do anything with it. DropBox will complain about it, but it won't be able to do anything about it. However, the question remains if or how the WAL file will get written if your main database is open exclusively. As I said before, I've used DB for a long while, been the EXCLUSIVE user on this particular database, I'm never writing to the database at anytime other than the machine I happen to be sitting at. I've only ever exclusively locked a file to one program because there COULD be a chance that I'd accidentally run multiple versions of the program in production mode, and I'd rather the error out on the second app rather than duplicate writes. If I realize that I have a lock on a file in my version control system at home, and I'm at work, I'll log into my machine at home, check in the changes, then check out at work, and continue on. However, if I'm at home and realize what I want to work on is at work... err.. well.... I'll go blow up some Kerbals (Kerbal Space Program) or drive manically into the back end of the competition in Gran Tourismo 5 and take the day off. ;) On Wed, Feb 12, 2014 at 12:59 PM, C M <[email protected]> wrote: > > > > I'd suggest looking into opening the database with an exclusive lock, > > > Can you say more about that? I'm not familiar with that option. > > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
