[w3c/IndexedDB] 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})` ? (Issue #372)

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_

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/372
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/issues/372@github.com>