Re: [IndexedDB] Implementation Discrepancies on 'prevunique' and 'nextunique' on index cursor

2012-10-08 Thread Odin Hørthe Omdal
On Sat, 06 Oct 2012 00:18:43 +0200, Israel Hilerio wrote: Thanks everyone for the explanations. Jonas, your last example clarified things for me. We'll file a bug on our side. I was going to point to some tests for it as well, to be extra helpful, but I hadn't pushed in a long time. No

RE: [IndexedDB] Implementation Discrepancies on 'prevunique' and 'nextunique' on index cursor

2012-10-05 Thread Israel Hilerio
On Wednesday, October 3, 2012 6:50 PM, Jonas Sicking wrote: >On Wed, Oct 3, 2012 at 9:48 AM, Joshua Bell wrote: >> On Wed, Oct 3, 2012 at 1:13 AM, Odin Hørthe Omdal wrote: >>> >>> So, at work and with the spec in front of me :-) >>> >>> >>> Odin claimed: >>> There is a note near the algori

Re: [IndexedDB] Implementation Discrepancies on 'prevunique' and 'nextunique' on index cursor

2012-10-03 Thread Jonas Sicking
On Wed, Oct 3, 2012 at 9:48 AM, Joshua Bell wrote: > On Wed, Oct 3, 2012 at 1:13 AM, Odin Hørthe Omdal wrote: >> >> So, at work and with the spec in front of me :-) >> >> >> Odin claimed: >> >>> There is a note near the algorithm saying something to that point, but >>> the definite text is up in

Re: [IndexedDB] Implementation Discrepancies on 'prevunique' and 'nextunique' on index cursor

2012-10-03 Thread Joshua Bell
On Wed, Oct 3, 2012 at 1:13 AM, Odin Hørthe Omdal wrote: > So, at work and with the spec in front of me :-) > > > Odin claimed: > > There is a note near the algorithm saying something to that point, but >> the definite text is up in the prose "let's explain IDB" section IIRC. >> > > Nope, this w

Re: [IndexedDB] Implementation Discrepancies on 'prevunique' and 'nextunique' on index cursor

2012-10-03 Thread Odin Hørthe Omdal
So, at work and with the spec in front of me :-) Odin claimed: There is a note near the algorithm saying something to that point, but the definite text is up in the prose "let's explain IDB" section IIRC. Nope, this was wrong, it's actually right there in the algorithm:

Re: [IndexedDB] Implementation Discrepancies on 'prevunique' and 'nextunique' on index cursor

2012-10-03 Thread Odin Hørthe Omdal
Without checking (I'm waiting for the bus in the rain) I can say we also do it like this. It is actually in the spec if you read it dead carefully, it's just not that obvious. It will first do the range getting, and then it will take the item on top sorted secondarily by value. And in an index