On Sun, Jul 1, 2012 at 12:12 PM, Simon Slavin <[email protected]> wrote:
Thanks for the help. Sorry to not get back sooner. >> 1) locked database (due to using SQLite Database Browser to change a >> database but not Saving it) >> 2) sqlite3.OperationalError: SQL logic error or missing database >> (happens very rarely. No idea why) >> 3) sqlite3.OperationalError: disk I/O error (also happens very rarely. >> No idea why) > > You already know the cause of number (1). I bet the same thing is causing > (2) and (3). I don't think a locked database (1) is causing (3), because I have observed the disk I/O error when the database is clearly not locked. It is also intermittent. I suspect it might be a real problem with my hard disk, which is old and nearly filled. (Which is actually useful, since I'd love to have a solution to this issue for users with similarly decrepit hard drives!). > One of the problems with reporting them here is that they are not SQLite > errors (i.e. > not one of the error codes listed here > <http://www.sqlite.org/c3ref/c_abort.html> > ) but seem to be errors generated by a framework or API you're using. Yes, these are the errors generated by the sqlite3 module in Python (formerly, I think, called pysqlite). There is probably a mapping out there somewhere between SQlite errors and these, and so I'll try to find it. Thanks. Che _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
