This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12114 - Blocked setVersion transactions should be aborted when their database is closed
Summary: Blocked setVersion transactions should be aborted when their database is closed
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-18 00:02 UTC by Jeremy Orlow
Modified: 2011-03-08 00:50 UTC (History)
2 users (show)

See Also:

Attachments

Description Jeremy Orlow 2011-02-18 00:02:28 UTC 
On Thu, Feb 17, 2011 at 3:58 PM, Pablo Castro <Pablo.Castro@microsoft.com> wrote:
>> What if you have two database connections open and both do a setVersion transaction and one calls .close (to yield to the other)?  Neither can start until one or the other actually is closed.  If a database is closed (not just close pending) then I think we need to abort any blocked setVersion calls.  If one is already running, it should certainly be allowed to finish before we close the database.

This sounds reasonable to me (special case and abort the transaction only for blocked setVersion transactions). We should capture it explicitly on the spec, it's the kind of little detail that's easy to forget.