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

Re: [IndexedDB] More questions about IDBRequests always firing (WAS: Reason for aborting transactions)

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 17 Feb 2011 11:12:32 -0800
Message-ID: <AANLkTimqs9SLOb2sPTETTLss=d=TQzJbkhTzWb9-iG2T@mail.gmail.com>
To: ben turner <bent.mozilla@gmail.com>
Cc: Jeremy Orlow <jorlow@chromium.org>, public-webapps WG <public-webapps@w3.org>
On Thu, Feb 17, 2011 at 11:02 AM, ben turner <bent.mozilla@gmail.com> wrote:
>>> Also, what should we do when you enqueue a setVersion transaction and then
>>> close the database handle?  Maybe an ABORT_ERR there too?
>>
>> Yeah, that'd make sense to me. Just like if you enque any other
>> transaction and then close the db handle.
>
> We don't abort transactions that are already in progress when you call
> db.close()... We just set a flag and prevent further transactions from
> being created.

Doh! Of course.

If the setVersion transaction has started then we should definitely
allow it finish, just like all other transactions. I don't have a
strong opinion on if we should let the setVersion transaction start if
it hasn't yet. Seems most consistent to let it, but if there's a
strong reason not to I could be convinced.

/ Jonas
Received on Thursday, 17 February 2011 19:13:35 GMT

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