-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/09/13 08:58, C M wrote: > If you think APSW would provide more details about just what went > wrong other than "SQLite logic error or missing database" (which, I > feel, doesn't tell me much at all), then I could potentially try it.
I'm in the process of adding error log support and should have it in a few days for you to try. You are welcome to email me directly or use the python-sqlite mailing list until the Python side of this is nailed down. "SQLite logic error or missing database" is the string associated with SQLITE_ERROR code which is used in a lot of places. SQLite does have extended codes that give more detail. pysqlite doesn't provide them but APSW does: http://apidoc.apsw.googlecode.com/hg/exceptions.html > Is setting up APSW and making the transition from pysqlite2's wrapper > fairly straightforward, or would I have to re-do all the database > queries? (Even so, I do them all in one utilities library, so perhaps > it would be not too much work). The actual querying etc is the same. (pysqlite borrowed how some of it is done from APSW :-) Note that pysqlite parses your SQL and tries to second guess what is going with transactions, and starts them behind your back. That is possibly causing problems for you too. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlIk8J8ACgkQmOOfHg372QTYCQCgi79D27GRMc6Tgjc8a+lI0Gt2 7IUAoOHGHlTKTJDmle82l5d98nWozmJ8 =PA/r -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
