Indexed Database API

Why is there no mechanism for paging results, a la SQL's "limit"?  If I want
entries in positions 140-159 from an index, I have to call continue() on a
cursor 139 times, which in turn unserializes 139 objects from my store that
I don't care about, which in FF4 is making a lookup in IndexedDB sometimes
take many seconds for even a few records.  It makes no sense--am I just
missing something in the spec?


Ben Dilts

Received on Friday, 4 March 2011 08:13:54 UTC