bpo-24139: Add support for SQLite extended result codes#28076
Conversation
|
This PR uses a different approach than Aviv's proposed patch in bpo. I use |
Sorry, something went wrong.
a4daae8 to
0275ffd
Compare
August 30, 2021 21:46
|
from the tests: |
Sorry, something went wrong.
Yes, |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @erlend-aasland for commit 63347d8 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
Sorry, something went wrong.
|
The |
Sorry, something went wrong.
SQLITE_CONSTRAINT_ROWID, SQLITE_READONLY_DBMOVED, and SQLITE_AUTH_USER
The SQLITE_RANGE error indices that the parameter number argument to one of the sqlite3_bind routines or the column number in one of the sqlite3_column routines is out of range. This should be considered a misuse of the SQLite API, so we translate it to InterfaceError, as defined by PEP 249.
|
Let me know if you have further remarks, @pablogsal :) |
Sorry, something went wrong.
https://bugs.python.org/issue24139