W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2007

[whatwg] SQL API error handling

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 25 Sep 2007 02:42:25 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0709250225150.21662@hixie.dreamhostps.com>
On Thu, 20 Sep 2007, Anne van Kesteren wrote:
> 
> The SQL API doesn't seem to define how to deal with errors, such as:
> 
>  * Bogus SQL statements

Defined.

>  * SQL statements that are not supported for security reasons

Defined to be the same as bogus statements.

>  * SQL statements that are not supported because they don't make sense

Same.

>  * SQL statements that fail to return anything

Why is this an error?

>  * Database that is not available for some reason

If the database isn't available, it should be created.

>  * Database that is full

This currently just reports an error with code 1, like everything else, 
but in due course we should get a useful set of error codes and define 
them. I'd love implementation feedback on what errors they are actually 
going to naturally end up wanting to report.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 24 September 2007 19:42:25 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:57 UTC