bpo-16379: Expose sqlite error code #1108
Conversation
auvipy
left a comment
There was a problem hiding this comment.
plz rebase!
Sorry, something went wrong.
|
Hi @palaviv Would you be interested to upgrade your PR to the last master? Thank you |
Sorry, something went wrong.
365ad2a to
c236045
Compare
May 8, 2019 12:22
|
Sure @matrixise. Do you think there is a chance for this to be merged? |
Sorry, something went wrong.
b9dc556 to
31467e3
Compare
May 9, 2019 09:55
|
If I remember https://bugs.python.org/issue24139 correctly, the issue was rather about exposing the extended error codes http://www.sqlite.org/c3ref/c_abort_rollback.html |
Sorry, something went wrong.
|
@dimaqq you are correct. This is a patch for https://bugs.python.org/issue16379. There is a different patch that depends on this change to solve https://bugs.python.org/issue24139. |
Sorry, something went wrong.
|
I'd really really like to have this feature... |
Sorry, something went wrong.
|
@palaviv: Can you rebase onto master and update your code to PEP 7 standards? Also, the |
Sorry, something went wrong.
|
@palaviv, are you planning on landing this PR? If not, would you mind if I reopened a PR with your changes cherry-picked onto it? |
Sorry, something went wrong.
This PR adds the sqlite error code and name to the exceptions raised by the sqlite3 module. Once this is merged my hope is to expose the sqlite extended error code as discussed in bpo-24139
https://bugs.python.org/issue16379