https://www.w3.org/Bugs/Public/show_bug.cgi?id=15721
Eliot Graff <eliot...@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #1 from Eliot Graff <eliot...@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 on the CC list for the bug.