Re: [w3c/IndexedDB] `getAll()` with both key and value (or index key and primary key) (#206) from Steven Becker on 2024-10-01 (public-webapps-github@w3.org from October 2024)

From: Steven Becker <notifications@github.com>
Date: Tue, 01 Oct 2024 13:02:06 -0700
To: w3c/IndexedDB <IndexedDB@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/IndexedDB/issues/206/2386949357@github.com>

TPAC 2024: We discussed the [getAllEntries() proposal referenced above](https://github.com/w3c/IndexedDB/issues/206#issuecomment-566205600), which we agreed is a good addition that should not be complex for browsers to implement.  We discussed how this proposal addresses some of the limitations reported by developers in this issue, including:

* Getting primary keys, values and indexes at the same time.
* Adding a direction option to support reverse iteration.
* Can reduce event loop overhead to potentially improve performance.

I've published an [explainer that goes into more detail](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/IndexedDbGetAllEntries/explainer.md).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/206#issuecomment-2386949357
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/issues/206/2386949357@github.com>

Received on Tuesday, 1 October 2024 20:02:09 UTC