Index records are stored in ascending order of key (index key) followed by
ascending order of value (primary key).
However, current IndexedDB API expose retrieving only by index key.
For example, the following operation on ‘tag‘ index of ‘article’ object
store will retrieve the first
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20257
Bug ID: 20257
Summary: IDBCursor should walk on secondary ordering of index
value
Classification: Unclassified
Product: WebAppsWG
Version: unspecified
Hardware: All
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20257
Joshua Bell jsb...@chromium.org changed:
What|Removed |Added
Status|NEW |RESOLVED
On Thu, Dec 6, 2012 at 6:47 AM, Joshua Bell jsb...@chromium.org wrote:
On Wed, Dec 5, 2012 at 7:50 AM, Kyaw Tun kyaw...@yathit.com wrote:
Index records are stored in ascending order of key (index key) followed
by ascending order of value (primary key).
However, current IndexedDB API
