Re: [w3c/IndexedDB] primaryKey compared to object store position is by value rather than key (#106)

@inexorabletash : You mentioned at https://github.com/w3c/IndexedDB/pull/105#issuecomment-257379096 that 

> The phrases you bold are the algorithms for comparing keys in general. The inputs are the *primaryKey* argument and the cursor's *object store position* which are both keys.

...yet I see *object store position* defined as "the cursor also has an object store position, which indicates the value of the previously found record in the index".

Although it of course makes sense that `primaryKey` is a key, I was just thrown off by the definition of *object store position* with which it was being compared indicating "the **value** of the previously found record in the index". I guess this just means that it is *pointing to* the value? I'm just not clear on why "value" is mentioned in that definition if it is just a key. Sorry for my haziness.

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

Received on Monday, 31 October 2016 18:48:26 UTC