This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author erlendaasland
Recipients erlendaasland
Date 2021-09-02.20:42:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1630615346.0.0.296018695296.issue45089@roundup.psfhosted.org>
In-reply-to
Content
Currently, two calls can raise exceptions in the _trace_callback() in Modules/_sqlite/connection.c:

  1. PyUnicode_DecodeUTF8() can raise an exception
  2. PyObject_CallOneArg() — calling the user callback — can raise an exception

Currently, we either PyErr_Print() the traceback, or we PyErr_Clear() it. In either case; we clear the current exception. The other SQLite callbacks pass some kind of return value back to SQLite to indicate failure (which is normally then passed to _pysqlite_seterror() via sqlite3_step() or sqlite3_finalize(), but the trace callback does not pass errors back to SQLite; we're unable to detect if the trace callback fails.
History
Date User Action Args
2021-09-02 20:42:26erlendaaslandsetrecipients: + erlendaasland
2021-09-02 20:42:26erlendaaslandsetmessageid: <1630615346.0.0.296018695296.issue45089@roundup.psfhosted.org>
2021-09-02 20:42:25erlendaaslandlinkissue45089 messages
2021-09-02 20:42:25erlendaaslandcreate