`getAll()` with both key and value (or index key and primary key)

[inexorabletash]

As a cursor replacement, getAll()/getAllKeys() has the issue that you need to pick - you can't get both the key and the value. For object stores this isn't so bad if inline keys are used, but still awkward. For indexes you can't even get the primary key.

Here's an example where getAll() could help but needs index key and primary key

https://stackoverflow.com/questions/44349168/speeding-up-indexeddb-search-with-multiple-workers

[inexorabletash]

A good name surfaced over in WICG/kv-storage#63 -

getAllEntries()

... which sort-of aligns with ECMAScript's array iterators: values(), keys(), and entries()

It would produce an array of two-element arrays.

[brettz9]

Which could nicely be fed into Object.fromEntries, passed into a Map, etc.

[inexorabletash]

Object stores are easy:

• getAllEntries() → [[primaryKey, value], ...]

Indexes are less straightforward:

• ??? → [[primaryKey, value], ...]
• ??? → [[indexKey, primaryKey], ...]
• ??? → [[indexKey, primaryKey, value], ...]

Having getAllEntries() on an Index produce [[primaryKey, value], ...] is closest to how getAllXXX() work on Indexes today, but there are use cases for the other permutations as well.

[inexorabletash]

I put a PR up for a straightforward version of getAllEntries() but see above re: index use cases. No consensus on this yet, I was mostly playing with refactoring the methods.

[inexorabletash]

TPAC 2019 Web Apps breakout:

• Consensus that we should solve this; calling getAll() and getAllKeys() and correlating is unfortunately common
• Object stores: getAllEntries() looks good
• Indexes: no good intuition

Follow-up: refine proposal for indexes

[inexorabletash]

Staring at this a bit more, I'd be tempted to have indexes produce:

• [[primaryKey, value, indexKey], ... ]

i.e. if you only pay attention to the first two elements, this looks just like getAllEntries() and can be used with Map constructor. If you need the index key it's there.