Richard Hipp wrote:
> Please try the changes in the branch at
> http://www.sqlite.org/src/info/8759a8e4d8 and let me know if they
> adequately cover your concerns.
Let's suppose user just did
cp -b somewhere/else/db opened.db
There *are* still file named opened.db, but it points to *different* file.
Sure, you can also compare stat() and fstat() to check if this is still same
file, ... but then you'll be asked for protection against
cp opened.db bar
while true; do
mv opened.db foo
mv bar opened.db
mv opened.db bar
mv foo opened.db
done
... and there are none. SQLite is responsible for protecting database against
corruption in case of concurrent modification by other SQLite instances. It
cannot protect against concurrent modification by other processes that does not
use SQLite locking protocol. And, IMO, it should not pretend it can.
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
