Re: [IndexedDB] More questions about IDBRequests always firing (WAS: Reason for aborting transactions) from ben turner on 2011-02-17 (public-webapps@w3.org from January to March 2011)

From: ben turner <bent.mozilla@gmail.com>
Date: Thu, 17 Feb 2011 11:02:48 -0800
To: Jonas Sicking <jonas@sicking.cc>
Cc: Jeremy Orlow <jorlow@chromium.org>, public-webapps WG <public-webapps@w3.org>
Message-ID: <AANLkTimhzdRatNFftq5P6jt=cnJ7Dpm=pgp33Y7ep=s6@mail.gmail.com>

>> 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.

-Ben

Received on Thursday, 17 February 2011 19:03:42 UTC