[whatwg] executeSql shouldn't have variable length arguments

Also, in case of no bind arguments, Gears allows the parameter to be
either empty or null or omitted (that not being an option in this
case).

-scott


On 10/5/07, Aaron Boodman <aa at google.com> wrote:
> To clarify, my proposed alternative is that the second argument should
> just be an array:
>
> executeSql(sql, ["foo", "bar", "baz"], callback);
>
> - a
>
> On 10/5/07, Aaron Boodman <aa at google.com> wrote:
> > Scott just pointed out to me that the current spec has executeSql
> > taking a variable number of arguments:
> >
> > http://www.whatwg.org/specs/web-apps/current-work/#executesql
> >
> > We tried this in Gears at first, but learned quickly that it was a
> > huge pain to work with. Dealing with the arguments collection in
> > javascript is very painful, so we ended up just passing arrays around
> > and converting them to the variable length at the last minute.
> >
> > Summary: variable length arguments seem cute at first, but end up
> > being more pain that they are worth.
> >
> > - a
> >
>

Received on Friday, 5 October 2007 17:08:36 UTC