[Bug 20257] IDBCursor should walk on secondary ordering of index value

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20257

Alec Flett <alecflett@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alecflett@chromium.org

--- Comment #12 from Alec Flett <alecflett@chromium.org> ---
I spent some time noodling on this and I think the example in comment 4 is the
most compelling. I'm not sure I buy the initial description as a useful case
(because for that specific usecase, it seems like you'd really just want to
call .get(primaryKey) and examine the indexed value. A cursor doesn't buy you
much here.

so for the inner-join-on-indexed-values, I think it would also be useful to
have this on IDBIndex.open[Key]Cursor as well - so that you don't have to open
a cursor in a bad place if you already have the primary key that you're jumping
to.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Saturday, 9 November 2013 00:07:37 UTC