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

[whatwg] Database storage and detecting success of COMMIT.

From: Aaron Boodman <aa@google.com>
Date: Thu, 18 Oct 2007 12:17:57 -0700
Message-ID: <278fd46c0710181217q237395c2i2077fbf7048b3cb@mail.gmail.com>
On 10/18/07, Scott Hess <shess at google.com> wrote:
> If the statement to executeSql() is invalid, then an exception will be
> raised immediately, which can be caught by wrapping the call to
> executeSql() with an exception handler.  If there is an error in the
> course of executing the statement, it will be exposed by the errorCode
> in the callback.  If there is no such error, the callback will be
> executed in the context of an implicit database transaction.  This
> would appear to leave no place from which to detect an error
> committing the transaction.  There is also no place to hang code to
> execute when the transaction is known to be successful.

Good one. Another reason I guess you need to separate the concept of
finishing a transaction from the concept of finishing a statement.

- a
Received on Thursday, 18 October 2007 12:17:57 UTC

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