W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: Indexed Database API

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 17 Mar 2011 15:16:24 -0700
Message-ID: <AANLkTik9bkvZLHEGaHwXpx8jXuCQ3gybEwbx5m9Wvx50@mail.gmail.com>
To: Pablo Castro <Pablo.Castro@microsoft.com>
Cc: Jeremy Orlow <jorlow@chromium.org>, ben turner <bent.mozilla@gmail.com>, "Olli@pettay.fi" <Olli@pettay.fi>, "public-webapps@w3.org" <public-webapps@w3.org>
On Thu, Mar 17, 2011 at 3:11 PM, Pablo Castro
<Pablo.Castro@microsoft.com> wrote:
>
> From: public-webapps-request@w3.org [mailto:public-webapps-request@w3.org] On Behalf Of Jeremy Orlow
> Sent: Tuesday, March 15, 2011 3:08 PM
>
>>> Filed: http://www.w3.org/Bugs/Public/show_bug.cgi?id=12310
>
> I'm not sure if this is a lot more valuable than just creating an index over whatever index key you want plus the primary key, and then seeking to the compound key of the last row in the previous page to resume scanning the next page of records. No strong pushback, just not sure this is worth the extra method.

The use-case here was  a paged UI that at the bottom allowed you to go
to any page. In this scenario you may not ever visit the page before
the one you want to display, and so you don't know which key to jump
to.

/ Jonas
Received on Thursday, 17 March 2011 22:17:27 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:43 GMT