W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2012

Re: IDBCursor should walk on secondary ordering of index value

From: Kyaw Tun <kyawtun@yathit.com>
Date: Thu, 13 Dec 2012 11:23:47 +0800
Message-ID: <CAFPCW96N73ZkB_1Abc07PP2jL=WFvoQ7RKuxqVYbGNexKZDegA@mail.gmail.com>
To: public-webapps@w3.org, Odin HÝrthe Omdal <odinho@opera.com>
> If you have that information from your other filtering, then why not just
> fetch them directly? Like IDBObjectStore.get(primary_key)?

The use case, here, is key joining without serialization, so that it
is very fast. We also want single scan. get method involve
serialization and resanning.

The use case, I talked about can be found in
http://dev.yathit.com/ydn-db/nosql-query.html in Sorted-merge join
section.
Received on Thursday, 13 December 2012 03:24:19 GMT

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