W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: [indexeddb] transaction commit failure

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 16 Aug 2011 08:07:52 -0700
Message-ID: <CA+c2ei9UZSSr2ePjPJ-2_WygChdpxxoF2Aj=z11LNFAehxnY7w@mail.gmail.com>
To: Shawn Wilsher <me@shawnwilsher.com>
Cc: "public-webapps@w3.org" <public-webapps@w3.org>
On Monday, August 15, 2011, Shawn Wilsher <me@shawnwilsher.com> wrote:
> On 8/15/2011 3:31 PM, Israel Hilerio wrote:
>> When the db is doing a commit after processing all records on the
>> transaction, if for some reason it fails, should we produce an error
>> event first and let the bubbling produce a transaction abort event or
>> should we only produce a transaction abort event. It seems that doing
>> the first approach would be more complete.
> I agree; the first approach seems better and I can't think of any reason
why it would be difficult to implement.
> The catch is that calling `preventDefault` will not prevent the abort,
which is (I think) different from how we handle other errors, right?

Yeah, I'm tempted to say that that is enough of a reason for simply firing
abort directly, but I could be convinced otherwise.

/ Jonas
Received on Tuesday, 16 August 2011 15:08:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:23 UTC