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

[whatwg] SQL API - SQLTransactionErrorCallback

From: Ian Hickson <ian@hixie.ch>
Date: Mon, 29 Oct 2007 22:37:25 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0710292236380.16783@hixie.dreamhostps.com>
On Mon, 29 Oct 2007, 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);

Actually I specifically didn't include the transaction because I can't see 
what you could do with it. You know which transaction it is, it's the one 
to which you are passing the method.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 29 October 2007 15:37:25 UTC

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