You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Typically APSW has more precise errors than Sqlite3, this is one of the exceptions.
When using create_scalar_function in deterministic mode, it is possible to throw an exception based on Sqlite constraints. In sqlite3 this raises a sqlite.NotSupportedError, but there is nothing specific in APSW. In fact, we're not sure what error is raised, so we lump it under apsw.Error. Some better things we can do:
Figure the specific error and capture/raise that as necessary
If there is no specific error, open a ticket, submit a PR to the upstream APSW library
Note
This is documented as a comment in the register_function code within this library
The text was updated successfully, but these errors were encountered:
Typically APSW has more precise errors than Sqlite3, this is one of the exceptions.
When using
create_scalar_function
indeterministic mode
, it is possible to throw an exception based on Sqlite constraints. In sqlite3 this raises asqlite.NotSupportedError
, but there is nothing specific in APSW. In fact, we're not sure what error is raised, so we lump it underapsw.Error
. Some better things we can do:Note
This is documented as a comment in the
register_function
code within this libraryThe text was updated successfully, but these errors were encountered: