On 2014/02/10 23:40, Stephen Chrzanowski wrote:
Personally, I don't buy that DropBox is the culprit as I've done this kind of thing a few times in a few applications of my own, however, I'm the single user that works on that single account, and any app that uses DB is usually under development and "closed" on any other geographical site. However, with the chance that the WAL file makes it down the wire, I could see that as being a problem if your application spits out small bits of data periodically and is being run in multiple places. DropBox, for me at least, realizes that another application has a handle on the database file and won't touch it, or overwrite anything. But the WAL file might make it through.
Yes, Dropbox realises when YOU are locking the file, the problem comes when you try to open the file while IT is locking it - something that will only really happen on an update (upload) or back-sync (download when it was changed elsewhere).
Heh, just try to open the DB on another computer it is sync'ed with while you have it open on your computer, then change stuff in both systems and close the apps (to release any SQLite locks)... You will quickly realise what a culprit Dropbox can be. Now imagine it for many users...
Further to this, imagine the WAL file (or any other of the temp files) gets synced without the DB file... or vice-versa, or you get another user's newer WAL file overwriting your own - a very probable situation.
[Note: This is not drop-box's fault, it has to do what it needs to do to ensure sharing tactics that suits most syncing needs] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
