In most error cases, we can use the error indicator from the SQLite database pointer when we raise exceptions. However, for some SQLite C APIs, we have to use the result code directly. This is the case for some of the blob APIs, where the error indicator is not stored on the database pointer.

Currently, our "set error" handler only handles the case where the error indicator is set on the database pointer. We also need an Modules/_sqlite private API for raising exception from the SQLite C API result codes.

See also #128507 (comment)

Linked PRs

• gh-129928: Rework sqlite3 error helpers #129929
• gh-129928: Raise more accurate exception for sqlite3 UDF creation misuse #129941