Re: IDBCursor should walk on secondary ordering of index value

> 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.