-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/02/2010 12:11 PM, Dave Dyer wrote: > Neither of these fits the scenario, which is multiple readers > contending for access to a networked disk.
See the second paragraph of http://www.sqlite.org/faq.html#q5 People have repeatedly found that when pushing network filesystem protocols you end up with bizarre errors due to the implementations of the protocol. If you can prove that both sides are always 100% correct then this would be interesting, but otherwise it is just another network filesystem issue to add to the list. For the record, this is what SQLite does to help verify correctness: http://www.sqlite.org/testing.html Additionally your email headers show you are using Windows. There is a propensity to run virus scanners, backup agents etc all watching filesystem activity which jump in at various points (eg scanning a file immediately after it is closed) that then cause further problems. For example Windows does not allow a file to be deleted if it is open by any process. (SQLite already has a workaround for that repeatedly trying deletes.) TLDR: 1. Do not use SQLite with a networked disk as there is no known implementation that is always correct. 2. If ignoring #1, prove that the network disk implementation is correct before blaming SQLite. 3. Watch out for other background tag-a-longs causing weird behaviour on Windows. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyni1YACgkQmOOfHg372QS89ACfegelzm0JCB9vuxoPJJjSo3k7 LTsAnihSza4lVH1tguCD0VH/b4Q4ci98 =vOgE -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
