Usability issues with IndexedDB

[scottohara]

No easy way to get all index keys

getAllKeys() only returns the store keys (primary keys)
openKeyCursor() iteration is too slow on large sets

• Consider adding some way to retrieve secondary keys when using IDBIndex.getAllKeys w3c/IndexedDB#71
• getAll() with both key and value (or index key and primary key) w3c/IndexedDB#206

JOINS

• Introduce a more general query mechanism beyond keys/ranges w3c/IndexedDB#45
• "Join" queries on multiple object stores w3c/IndexedDB#92
• Combining cursors / query execution engine w3c/IndexedDB#298

Arbitrary ORDER BY

• Allow sorting within indexes w3c/IndexedDB#138

Partial key searches

Given: store.createIndex(["a", "b"])

The only way to find all records where a = "foo" (regardless of b) is:

IDBKeyRange.bound(["foo"], ["foo", "~"]);

(where "~" is the highest ascii character).

It would be preferable to be able to use something like IDBKeyRange.only("foo") instead.

• Introduce a more general query mechanism beyond keys/ranges w3c/IndexedDB#45

No support for OR key searches

i.e. key = A or key = B

Proposed solution seems to be IDBKeyList

• Support queries retrieving disjoint sets of keys w3c/IndexedDB#19

Indexing into nested arrays

• Key Paths: Support iteration step operator w3c/IndexedDB#35

Index keys can’t be boolean

e.g. active: true

• boolean should be a valid key w3c/IndexedDB#76