https://www.w3.org/Bugs/Public/show_bug.cgi?id=20257
Joshua Bell changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20257
Joshua Bell changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|LATER
> 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
On Wed, 05 Dec 2012 16:50:12 +0100, Kyaw Tun 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,
On Thu, Dec 6, 2012 at 6:47 AM, Joshua Bell wrote:
>
>
> On Wed, Dec 5, 2012 at 7:50 AM, Kyaw Tun wrote:
>
>> Index records are stored in ascending order of key (index key) followed
>> by ascending order of value (primary key).
>>
>>
>> However, current IndexedDB API expose retrieving only by in
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20257
Joshua Bell changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20257
Bug ID: 20257
Summary: IDBCursor should walk on secondary ordering of index
value
Classification: Unclassified
Product: WebAppsWG
Version: unspecified
Hardware: All
On Wed, Dec 5, 2012 at 7:50 AM, Kyaw Tun wrote:
> Index records are stored in ascending order of key (index key) followed by
> ascending order of value (primary key).
>
>
> However, current IndexedDB API expose retrieving only by index key.
>
>
> For example, the following operation on ‘tag‘ inde
Index records are stored in ascending order of key (index key) followed by
ascending order of value (primary key).
However, current IndexedDB API expose retrieving only by index key.
For example, the following operation on ‘tag‘ index of ‘article’ object
store will retrieve the first occurrent
