11094 2010-10-19 13:47:36 +0000 [IndexedDB] IDBIndex.get* don't define which item is returned in the case of duplicates 2010-11-08 11:34:57 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC All RESOLVED FIXED P2 normal --- 1 jorlow jonas jonas mike public-webapps public-webapps-bugzilla oldest_to_newest 41549 0 jorlow 2010-10-19 13:47:36 +0000 It's possible for indexes to be non-unique in which case IDBIndex.get* may lookup one of several entries. We should specify which is returned in a deterministic way. It should probably be connected to the order in which cursors return duplicates as well. 41592 1 jonas 2010-10-19 23:47:31 +0000 I recall discussing this on the list. Like you point out, the same issue exists when using a cursor created using IDBIndex.createObjectCursor. Here we need to define which order duplicates are iterated in. IMO the order should be the key order in the objectStore. I.e. items in indexes are first ordered by their keyPath value, then by the objectStores key value. get* functions should return the first item according to this order. 41910 2 jonas 2010-11-01 04:53:16 +0000 Working at rewriting cursor handling, especially related to indexes. 42254 3 jonas 2010-11-08 11:34:57 +0000 Should be fixed by http://dvcs.w3.org/hg/IndexedDB/rev/8716288a4fe1 Would be great if someone could check that it looks correct.