Re: [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)

• From: Joshua Bell <notifications@github.com>
• Date: Thu, 20 Jan 2022 11:04:19 -0800
• To: w3c/IndexedDB <IndexedDB@noreply.github.com>
• Cc: Subscribed <subscribed@noreply.github.com>
• Message-ID: <w3c/IndexedDB/issues/372/1017829905@github.com>

Seems to be a spam bot.

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

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

Received on Thursday, 20 January 2022 19:04:31 UTC