W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > February 2012

[Bug 15721] [IndexedDB] Specify when calling transaction() should throw due to being called "too early"

From: <bugzilla@jessica.w3.org>
Date: Wed, 29 Feb 2012 18:02:15 +0000
To: public-webapps-bugzilla@w3.org
Message-Id: <E1S2nqx-0005xe-UV@jessica.w3.org>

Eliot Graff <eliotgra@microsoft.com> changed:

           What    |Removed                     |Added
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #1 from Eliot Graff <eliotgra@microsoft.com> 2012-02-29 18:02:15 UTC ---
Section 3.1.7 now reads in part as follows (see last sentence for change):

A VERSION_CHANGE transaction can never run concurrently with other
transactions. When a VERSION_CHANGE transaction is created, the implementation
must wait to start the VERSION_CHANGE transaction until no other transactions
against the same database are running. As long as the VERSION_CHANGE
transaction is pending, the implementation must wait before starting any other
transactions against the same database until the VERSION_CHANGE transaction is
finished. However, a new transaction MAY be started as soon as the oncomplete
handler is invoked.

Live as of Editor's draft Feb 29.

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 29 February 2012 18:02:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:04:22 UTC