new getAllRecords() API

[lvivski]

Not really an issue but browsers are going add a new .getAllRecords API w3c/IndexedDB#461. Might be useful for Dexie.

[dfahlander]

Thanks! This will open up for improving performance in dexie. I'll keep a close eye on it.

[nickchomey]

This was added to chromium browsers in the past 5 months https://caniuse.com/wf-getallrecords. Perhaps could be used in a polyfill pattern - browsers that support it use it, otherwise use the existing mechanism?

[nickchomey]

This is now in Interop 2026, so Firefox and Safari will be implementing it at some point this year.

Other resources:

• https://developer.mozilla.org/en-US/docs/Web/API/IDBIndex/getAllRecords
• https://patrickbrosset.com/articles/2024-11-19-even-faster-indexeddb-reads-with-getallrecords/
• https://microsoftedge.github.io/Demos/idb-getallrecords/ - benchmark test. 2x faster for me, and 5x faster in reverse

[liz709]

Great news that this is now in Interop 2026! 🎉

Here's a quick analysis of how getAllRecords() could be integrated into Dexie:

Where it would help

The main benefit is in DBCore's query() operation, especially for:

• table.toArray()
• table.where(...).toArray()
• collection.sortBy() (reverse iteration with prev direction)

Currently these use cursors or getAll() + getAllKeys() separately.

Implementation approach

// In src/dbcore/dbcore-indexeddb.ts

// Feature detection
const supportsGetAllRecords = typeof IDBObjectStore.prototype.getAllRecords === 'function';

// In query() implementation:
if (supportsGetAllRecords && !query.filter) {
  const records = await idbStore.getAllRecords({
    query: keyRange,
    count: limit,
    direction: reverse ? 'prev' : 'next'
  });
  return {
    result: records.map(r => r.value),
    // Can also return keys efficiently now!
  };
}
// else: fallback to cursor iteration

Benefits

• 2-5x faster reads (especially reverse iteration)
• Single IDB request instead of cursor loop
• Keys included - useful for table.toCollection().primaryKeys()

Considerations

• Need fallback for Safari/Firefox until they implement it
• The direction option is perfect for orderBy().reverse()
• Filter functions still need cursor iteration

I can start on a draft PR if you'd like, David! 🛠️

[dfahlander]

@liz709 The benefits would be for reverse collection only. The .primaryKeys() method already use getAllKeys() for forward direction. (getAllKeys() actually gets the primary keys despite it's confusing naming).

Please create a PR @liz709

[liz709]

Created PR #2252 implementing this! 🎉

The implementation uses getAllRecords() for reverse queries when available, with cursor fallback for older browsers.

[nickchomey]

FYI, some explorations in rxdb show that getAllRecords isn't necessarily faster - especially if you use inline keys via keyPath (which dexie seems to do).

But, as was mentioned, the reverse collection would surely benefit.