- From: Evan Stade <notifications@github.com>
- Date: Wed, 02 Aug 2023 15:25:53 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 2 August 2023 22:25:58 UTC
@evanstade commented on this pull request. > The {{IDBOpenDBRequest/upgradeneeded!!event}} event isn't fired, and thus the [=/upgrade transaction=] isn't started, until all other [=/connections=] to the same [=/database=] are closed. This ensures that all previous transactions are [=transaction/finished=]. As long - as an [=/upgrade transaction=] is running, attempts to open more + as an [=/upgrade transaction=] is [=transaction/live=], attempts to open more [=/connections=] to the same [=/database=] are delayed, and any attempts to use the same [=/connection=] to start additional transactions by calling {{IDBDatabase/transaction()}} will throw an exception. Thus [=/upgrade transactions=] not only ensure that no I agree that dropping it might ultimately be less confusing since it's essentially restating information from elsewhere in the doc, but less clearly (imo). The new form is better too. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/IndexedDB/pull/409#discussion_r1282472626 You are receiving this because you are subscribed to this thread. Message ID: <w3c/IndexedDB/pull/409/review/1559923458@github.com>
Received on Wednesday, 2 August 2023 22:25:58 UTC