-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/10/2014 10:22 AM, Mike McWhinney wrote: > So SQLite shouldn't be used at all on a network? Aren't there any > other provisions to handled the locking errors if/when they occur?
Network filesystems do not implement locking and other operations *exactly* the same as for (most) local filesystems. This is done due to the protocols involved, race conditions, performance considerations, latencies, and various other reasons. You are seeing the locking errors as a symptom of this. If you use SQLite with a network then your data will eventually end up corrupted. Yes it is possible to sweep some stuff under the rug but that does not mean corruption won't happen. SQLite won't be able to prevent it, and often may not detect it for a while. This page describes how SQLite does locking as well as pointing to some newer alternatives: https://www.sqlite.org/lockingv3.html See also: https://www.sqlite.org/whentouse.html Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRhBm8ACgkQmOOfHg372QTcLgCfblMaFauIRgE83WOcF9z2M6BV BMYAnRSP1KwC+69vb5fUMsGeGbdImHU1 =1mbq -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
