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: Fri, 28 Jan 2011 16:33:57 -0800
Message-ID: <AANLkTikWE5CGmJPUoAnvsxjTYVnxg29NbSz=68xM2sqX@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: public-webapps WG <public-webapps@w3.org>
We do that as well.

What's the best way to do it API wise?  Do we need to add an
IDBTransactionError object with error codes and such?

J

On Fri, Jan 28, 2011 at 4:31 PM, Jonas Sicking <jonas@sicking.cc> wrote:

> On Fri, Jan 28, 2011 at 2:35 PM, Jeremy Orlow <jorlow@chromium.org> wrote:
> > Given that transactions can be aborted because of explicit action,
> internal
> > errors, quota errors, and possibly other things in the future, I'm
> wondering
> > if we should add some way for people to find out why the transaction was
> > aborted.
> > Thoughts?
>
> Hmm.. not a bad idea. We also abort transactions if the user leaves
> the current page in the middle of a transaction. Don't remember if the
> spec requires this or not, but it might make sense to do so.
>
> / Jonas
>
Received on Saturday, 29 January 2011 00:34:47 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:43 GMT