W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: [IndexedDB] Reason for aborting transactions

From: Jeremy Orlow <jorlow@chromium.org>
Date: Wed, 9 Feb 2011 17:21:58 -0800
Message-ID: <AANLkTimGP1WAtt3tjB8GsK25At+rUmfUHobjJmoczFk8@mail.gmail.com>
To: ben turner <bent.mozilla@gmail.com>
Cc: Jonas Sicking <jonas@sicking.cc>, Cameron McCormack <cam@mcc.id.au>, public-webapps WG <public-webapps@w3.org>
On Wed, Feb 9, 2011 at 5:17 PM, ben turner <bent.mozilla@gmail.com> wrote:

> Hm, Jeremy is right, If you want to look just at the transaction and
> see why it aborted you can't rely on errorCode. Ick.
> The only thing I'd change then is the abortMessage property. It's
> easier to tell why your transaction aborted with the error code, and
> I'd hate people doing string comparisons instead of checking the error
> code. And what about localization?

Normal exceptions have error messages that are not consistient across
implementations and are not localized.  What's the difference?

For stuff like internal errors, they seem especially important.

Received on Thursday, 10 February 2011 01:22:47 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 February 2015 14:36:48 UTC