[whatwg] SQL API and changeVersion() with no callbacks
Ian Hickson
ian at hixie.ch
Fri Oct 26 15:23:57 PDT 2007
On Thu, 25 Oct 2007, Brady Eidson wrote:
>
> For the sake of simplicity in the API, I see no reason why there
> couldn't be a single version of changeVersion() with the 2 strings and 2
> callbacks. Then if a user truly wanted to call changeVersion() but
> wasn't interested in the results, they could just pass null for both of
> the callbacks.
Very good point. I have removed the overloads here. This is not going to
be frequently called, so why not require the callbacks.
> I suppose the same could be said about executeSql().
Well... I can certainly see people queuing up a bunch of requests and
dealing with the errors at the end in the transaction error handler. I am
open to requiring that that have an explicit "null" though. Who do other
people think?
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg
mailing list