[Webkit-unassigned] [Bug 60763] IndexedDB chooses wrong record on PREV_NO_DUPLICATE index key cursor

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=60763


Hans Wennborg <hans at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jsbell at chromium.org




--- Comment #5 from Hans Wennborg <hans at chromium.org>  2011-10-25 03:41:06 PST ---
This patch is old, and doesn't apply anymore since the SQLite back-end is gone, but it would be nice to get the test.

I'm not sure what the correct behavior is here. For PREV_NO_DUPLICATE, the spec says: "[...]  this cursor should yield all records, not including duplicates and its direction is monotonically decreasing order of keys. For every key with duplicate values, only the first record is yielded."

What does *first record* mean in this context? The first record that is found when traversing the records in monotonically decreasing order of keys, or the first record as in lowest record? This test seems to expect the latter, but we do the former.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.