➜

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 vstinner
Recipients ned.deily, python-dev, vstinner
Date 2013-07-21.11:13:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1374405228.69.0.827683982126.issue18519@psf.upfronthosting.co.za>
In-reply-to
Content 
It's not a crash, but an assertion that I added recently: it means that a previous Python exception is not handled correctly.

The problem is that a first call to _authorizer_callback() raised a Python exception and returned SQLITE_DENY, but sqlite called _authorizer_callback() again (with the Python exception set).

According to the doc: "SQLITE_DENY to cause the entire SQL statement to be rejected with an error":
http://www.sqlite.org/c3ref/set_authorizer.html

So I don't expect _authorizer_callback() to be called again if the previous call returned SQLITE_DENY. Whatever, this issue should be fixed by the changeset 026593cbc006.
History
Date User Action Args
2013-07-21 11:13:48vstinnersetrecipients: + vstinner, ned.deily, python-dev
2013-07-21 11:13:48vstinnersetmessageid: <1374405228.69.0.827683982126.issue18519@psf.upfronthosting.co.za>
2013-07-21 11:13:48vstinnerlinkissue18519 messages
2013-07-21 11:13:48vstinnercreate