W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

Re: [web databases] SQLStatementErrorCallback

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 1 Dec 2009 02:07:53 +0000 (UTC)
To: Dumitru Daniliuc <dumi@chromium.org>
Cc: public-webapps <public-webapps@w3.org>
Message-ID: <Pine.LNX.4.62.0912010204320.4718@hixie.dreamhostps.com>
On Fri, 4 Sep 2009, Dumitru Daniliuc wrote:
> 
> When talking about statement error callbacks (point #6, section 4.3.2), the
> spec says:
> 1. If the error callback returns false, then move on to the next statement,
> if any, or onto the next overall step otherwise.
> 2. Otherwise, the error callback did not return false, or there was no error
> callback. Jump to the last step in the overall steps.
> 
> What should happen if the callback doesn't return anything (undefined)?
> Should we jump to the transaction error callback? Can/should we clarify this
> in the spec too?

If it doesn't return false, then the second step you quote above (numbered 
3 in the spec) applies, no? I don't understand how this is unclear.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 1 December 2009 02:08:28 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:35 GMT