Suppose you have a sqlite DB which might be accessed over a network, and might 
also be accessed locally.  My understanding is that it would be disastrous if 
one client used proxy locking and the other did not - there would effectively 
be no lock.

The "prefer proxy locking" logic has a strange mode where it uses the runtime 
environment to override the default behavior, which is to use proxy locking 
only for remote file systems.   

I think this is too important to be left to a runtime environment variable.  If 
the application opens the database with SQLITE_OPEN_AUTOPROXY then proxy 
locking should be use unconditionally.
sqlite-users mailing list

Reply via email to