On Wed, 1 Mar 2017, Simon Slavin wrote:
On 1 Mar 2017, at 7:27pm, Bob Friesenhahn <bfrie...@simple.dallas.tx.us> wrote:
What is the recommended approach to diagnosing "Database is locked" errors and
determining the guilty party?
Are you checking the result codes returned by all SQLite commands you give to
make sure they are SQLITE_OK ?
Some of our C software is very good at doing this, and some C code is
not quite as good. Our Python code should be robust at reporting
problems since we are using APSW and Python exceptions.
We do capture output from sqlite's tracing facility, including error
reports.
I am not sure of all of the conditions which might result in "Database
is locked". For example, if the results of a query are being iterated
through and the reader stops iterating part way through the result
set, might this cause "Database is locked" for writers?
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
