[Bug 25251] New: Transaction ordering for readonly transactions


            Bug ID: 25251
           Summary: Transaction ordering for readonly transactions
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
          Assignee: dave.null@w3.org
          Reporter: jsbell@google.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

Tracking bug for this conversation:


Short version, c/o Jonas:

"Specifically, there is nothing that says that if a readonly transaction is
created after a readwrite transaction, that the readonly transaction runs after
the readwrite transaction. This is true even if the two transactions have
overlapping scopes."

.. and then further details about this, since Chrome takes advantage of this
but it can be unexpected for developers.

You are receiving this mail because:
You are on the CC list for the bug.

Received on Thursday, 3 April 2014 18:21:00 UTC