-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 He needs to give the exception traceback which will show what is happening at the time.
A common mistake with newish Python programmers is to catch all exceptions, and then keep going which also hides the exception tracebacks. On 01/09/13 15:12, Richard Hipp wrote: > Does Python have an interface to the error and warning log mechanism > of SQLite? (http://www.sqlite.org/errlog.html) Can you turn that on? > It will probably give more details about what it happening. pysqlite is the standard Python sqlite3 module and doesn't expose that functionality. (It also hasn't had a new release in over two years.) It tries to make SQLite look like the standard Python DBAPI and maps the SQLite errors into those fewer DBAPI exceptions. APSW (disclosure: I am the author) does provide the SQLite errors in a 1:1 mapping to exceptions. The error log could be used in theory, but is impractical because it has to be setup before any other SQLite call. There doesn't appear to be any reason why it can't be changed after the library is initialised. I'll see if I can add something more useful to the next APSW release. Note that the APSW API is similar to pysqlite, but not the same. It behaves the SQLite way rather than the DBAPI way. http://apidoc.apsw.googlecode.com/hg/pysqlite.html Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlIj0vYACgkQmOOfHg372QSYrwCcCuJyMqsUiS5SYVFpeYll72d+ Z0oAoJSoWZNanNAxoBMUzjXHMfyEFmj1 =eyCs -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
