➜

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 serhiy.storchaka
Recipients berker.peksag, erlendaasland, serhiy.storchaka
Date 2021-08-05.11:54:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1628164492.41.0.705893137688.issue44839@roundup.psfhosted.org>
In-reply-to
Content 
Currently, any exception raised in user-defined function set the general SQLITE_ERROR error which then produce sqlite3.OperationalError.

For example, if the user function returns a string or bytes object larger than INT_MAX you get OperationalError, but if it is less than INT_MAX and larger than the SQLite limit (configurable, 1000000000 by default) you get DataError. If a memory error occurred in Python code you get OperationalError, but if it is occurred in the SQLite code you get MemoryError.

The proposed PR sets corresponding SQLite error codes for MemoryError and OverflowError in user-defined functions. They will produce MemoryError and DataError in Python.
History
Date User Action Args
2021-08-05 11:54:52serhiy.storchakasetrecipients: + serhiy.storchaka, berker.peksag, erlendaasland
2021-08-05 11:54:52serhiy.storchakasetmessageid: <1628164492.41.0.705893137688.issue44839@roundup.psfhosted.org>
2021-08-05 11:54:52serhiy.storchakalinkissue44839 messages
2021-08-05 11:54:52serhiy.storchakacreate