#1117: Add IndexedDB getAllRecords() method and update getAll()/getAllKeys() to support direction option
Discussions
Log in to see TAG-private discussions.
Discussed
Jul 7, 2025 (See Github)
Christian: Only halfway through, getAllRecords() seems fine, but the changing the existing methods needs a deeper look.
Lola: Do people want to join this issue?
Martin: I would love to join. Also think that the changes to existing methods need a deeper look.
Discussed
Jul 14, 2025 (See Github)
(Martin & Christian not here)
Discussed
Jul 21, 2025 (See Github)
Christian: Didn't have time yet, will take care of it until next week.
End of official agenda, bringing over issues from Breakout A.
OpenedJun 26, 2025
こんにちは TAG-さん!
I'm requesting a TAG review of the getAllRecords() method and the direction option for IndexedDB.
Proposes a new operation, getAllRecords(), which combines getAllKeys() with getAll() to enumerate both primary keys and values at the same time. For an IDBIndex, getAllRecords() also provides the record's index key in addition to the primary key and value. Lastly, getAllRecords() offers a new direction option to enumerate records sorted by key in descending order. To add the direction option to the existing getAll() and getAllKeys() operations, this explainer proposes new function overloads that accept the same argument as getAllRecords(): the IDBGetAllOptions dictionary.
Further details:
Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1117