Re: [IndexedDB] .value of no-duplicate cursors

When I think of this, I think of it returning the first item for a
particular value.  I can't think of any use cases where it'd matter either
way though.  Can you?


On Thu, Nov 11, 2010 at 7:13 PM, ben turner <> wrote:

> On Thu, Nov 11, 2010 at 8:07 AM, Jonas Sicking <> wrote:
> > The reason I specced it they way I did, with the "lowest" key always
> > being used, is that this way a NEXT_NO_DUPLICATE and a
> > PREV_NO_DUPLICATE cursor iterate the same entries. It seems unexpected
> > that reversing direction would return different results?
> I agree.
> -Ben

Received on Thursday, 11 November 2010 19:49:47 UTC