Re: [sqlite] DOMAIN new error code

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/10/11 02:00, Jean-Christophe Deschamps wrote: > That's an half-backed solution. I know of no application which test > error codes AND THEN test error message _content_ before selecting a > way to deal with the error. The application won't but

Re: [sqlite] DOMAIN new error code

On 17 Oct 2011 at 10:00, Jean-Christophe Deschamps wrote: > At least it would gives a fairly good hint as to what to look for and > where to look. You know that some extension function was passed an > out-of-range argument during the course of the last operation. From >

Re: [sqlite] DOMAIN new error code

That is the default text for the error code, but your extension should provide different text. That's an half-backed solution. I know of no application which test error codes AND THEN test error message _content_ before selecting a way to deal with the error. Most of the times, the

Re: [sqlite] DOMAIN new error code

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16/10/11 17:21, Jean-Christophe Deschamps wrote: > rather than being confronted to the uninformative SQLITE_ERROR "SQL > error or missing database". That is the default text for the error code, but your extension should provide different text.

[sqlite] DOMAIN new error code

I have the need to use some math extension functions. While testing them I found it very difficult to select an informative error code in case of a domain error, like sqrt(-1). Would it be sensible to create a new generic error code in some next release for extension functions to report such