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

[whatwg] Comments on updated SQL API

From: Scott Hess <shess@google.com>
Date: Wed, 17 Oct 2007 13:14:15 -0700
Message-ID: <696e4b7c0710171314udecdc07n343cddb8c248c897@mail.gmail.com>
On 10/17/07, Maciej Stachowiak <mjs at apple.com> wrote:
> I'm not sure what other reasons Scott sees for (2). I do think it
> would aid authoring clarity to have the word "transaction" in the API,
> even if the model of how they are managed is much the same as
> currently (so you can't forget to close it) and even if a
> transactionless API is not added.

I think my concern is in two related bits:

A) As things currently stand, the developer simply can't roll their
own transaction structure.  Passing BEGIN, COMMIT, or ROLLBACK to
executeSql() doesn't do anything sensible.  It's possible you could
somehow do something using temporary tables, but that's going to be
really dependent on your underlying SQL implementation's capabilities.

B) Transactions are a meaningful concept in SQL, and we're entangling
that concept with an implementation detail of how the API is
implemented.

I'm gradually getting to where I don't feel strongly about B.  If you
don't want a transaction, you can have serial calls to executeSql().
If you want serial calls that are dependent, you can call
closeTransaction() before making the next executeSql().  I agree that
the following might be more self-documenting:

  db.transaction(function () {
    db.executeSql(...);
  });

On A, I'm still nervous.

-scott
Received on Wednesday, 17 October 2007 13:14:15 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:37 UTC