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

[whatwg] SQL API - SQLTransactionErrorCallback

From: Brady Eidson <beidson@apple.com>
Date: Mon, 29 Oct 2007 14:41:51 -0700
Message-ID: <6E4960DA-3D05-4115-86F7-B7275085D278@apple.com>
As I read this email, I realize we'd be making  
SQLTransactionErrorCallback and SQLStatementErrorCallback have  
identical properties, perhaps making them candidates for a pruning.
I don't know what the name of the sole object would be, however, as  
the context would be quite different depending on if it were a  
statement err'ing out or a transaction.

~Brady

On Oct 29, 2007, at 2:33 PM, Brady Eidson wrote:

> A SQLTransactionErrorCallback object has a single method:
> boolean handleEvent(in SQLError error);
>
> This method is meant for both notifying of a failure in the  
> transaction as well as for deciding it's fate - should we commit  
> what we have, or just roll it back?
> However, there's one problem - how does the script and it's  
> SQLTransactionErrorCallback know which transaction is in question?
>
> I propose we change SQLTransactionErrorCallback.handleEvent() to  
> have the same signature as the SQLStatementErrorCallback, which is:
> boolean handleEvent(in SQLTransaction transaction, in SQLError error);
>
> Thanks,
> ~Brady
Received on Monday, 29 October 2007 14:41:51 UTC

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