[whatwg] SQL API error handling

Aside: the net gain from shortening INVALID_STATE_ERROR to INVALID_STATE_ERR
is 2/19; is it worth sacrificing readability for 11% length?

-----Original Message-----
From: whatwg-bounces@lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Brady Eidson
Sent: Wednesday, October 17, 2007 12:08 AM
To: Geoffrey Garen
Cc: Scott Hess; Maciej Stachowiak; Ian Hickson; WHATWG
Subject: Re: [whatwg] SQL API error handling

INVALID_STATE_ERR is already overloaded and I think the corruption  
case is a particularly problematic one - I guess what I'm after is a  
special condition for the corruption case built in to the spec.

Received on Wednesday, 17 October 2007 12:50:30 UTC