We are sometimes encountering permanent "Database is locked" errors
from sqlite 3.10.2. After the database gets in this state it is not
possible to write to it or read from it. It is not possible to use
sqlite's built in backup mechanism since it produces a backup file of
zero bytes.
What is the recommended approach to diagnosing "Database is locked"
errors and determining the guilty party?
Is there a way to clear the condition which causes "Database is
locked" errors?
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
