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

Re: [indexeddb] Missing TransactionInactiveError Exception type for count and index methods

From: Joshua Bell <jsbell@chromium.org>
Date: Mon, 23 Jan 2012 17:17:47 -0800
Message-ID: <CAD649j6LBpN99M05R=vRnoBj+rsvwxNihWwd=Mz--3Lg42Nhpw@mail.gmail.com>
To: "public-webapps@w3.org" <public-webapps@w3.org>
On Mon, Jan 23, 2012 at 4:12 PM, Israel Hilerio <israelh@microsoft.com>wrote:

> In looking at the count method in IDBObjectStore and IDBIndex we noticed
> that its signature doesn't throw a TransactionInactiveError when the
> transaction being used is inactive.  We would like to add this to the spec.

Agreed. FWIW, this matches Chrome's behavior.

> In addition, the index method in IDBObjectStore uses InvalidStateError to
> convey two different meanings: the object has been removed or deleted and
> the transaction being used finished.  It seems that it would be better to
> separate these into:
> * InvalidStateError when the source object has been removed or deleted.
> * TransactionInactiveError when the transaction being used is inactive.
> What do you think?  I can open a bug if we agree this is the desired
> behavior.

Did this come out of the discussion here:


If so, the rationale for which exception type to use is included, although
no-one on the thread was deeply averse to the alternative. If it's a
different issue can give a more specific example?
Received on Tuesday, 24 January 2012 01:18:15 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:38 UTC