http://www.w3.org/Bugs/Public/show_bug.cgi?id=12114
Summary: Blocked setVersion transactions should be aborted when
their database is closed
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Indexed Database API
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected], [email protected]
On Thu, Feb 17, 2011 at 3:58 PM, Pablo Castro <[email protected]>
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.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
