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

Re: IDBCursor should walk on secondary ordering of index value

From: Odin Hørthe Omdal <odinho@opera.com>
Date: Tue, 11 Dec 2012 16:52:05 +0100
To: public-webapps@w3.org
Message-ID: <op.wo5s03oq49xobu@odinho-fido>
On Wed, 05 Dec 2012 16:50:12 +0100, Kyaw Tun <kyawtun@yathit.com> wrote:
> It will be good if IndexedDB API provide like:
> IDBCursor_article_tag.continue(index_key, primary_key)
> It is a bit strange since the result is again primary_key. We already  
> know primary_key from other filter condition.

It's a bit strange, I'm not sure I understand.

If you have that information from your other filtering, then why not just  
fetch them directly? Like IDBObjectStore.get(primary_key)?

Odin Hørthe Omdal (Velmont/odinho) · Core, Opera Software, http://opera.com
Received on Tuesday, 11 December 2012 15:52:40 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:50 UTC