In the `openCursor()` case, is the lower-bound of the key range implicitly the index key if primaryKey is specified (and thus it's an error if a open lower bound is specified), or should the range and starting position be decoupled and require both the key and primaryKey to be explicit specified e.g. `openCursor(null, null, {key: x, primaryKey: y})` ?

w3c / IndexedDB

Indexed Database API

https://w3c.github.io/IndexedDB/

Other

240 stars 62 forks source link

In the `openCursor()` case, is the lower-bound of the key range implicitly the index key if primaryKey is specified (and thus it's an error if a open lower bound is specified), or should the range and starting position be decoupled and require both the key and primaryKey to be explicit specified e.g. `openCursor(null, null, {key: x, primaryKey: y})` ? #372

Closed Mguiteria closed 2 years ago

Mguiteria commented 2 years ago

In the openCursor() case, is the lower-bound of the key range implicitly the index key if primaryKey is specified (and thus it's an error if a open lower bound is specified), or should the range and starting position be decoupled and require both the key and primaryKey to be explicit specified e.g. openCursor(null, null, {key: x, primaryKey: y}) ?

Originally posted by @inexorabletash in https://github.com/w3c/IndexedDB/issues/14#issuecomment-113323808

inexorabletash commented 2 years ago

Seems to be a spam bot.