[IndexedDB] Support N-dimensional queries on indexes (#40)

Short summary, if an index's array keypath represents multiple dimensions, using an IDBKeyRange.bound([minX, minY, ...], [maxX, maxY, ...]) doesn't behave as some developers expect. This has come up a few times on Stack Overflow:

http://stackoverflow.com/questions/21731347/indexeddb-idbkeyrange-compound-multiple-index-not-working

http://stackoverflow.com/questions/16522115/indexed-db-cursor-ranges-on-mulitiple-properties

This is because IDBKeyRange represents a one-dimensional range.

A general N-dimensional query using cursors is plausible but subtle:

https://gist.github.com/inexorabletash/704e9688f99ac12dd336

We could support this scenario with another query object type, array of ranges, or ...?



---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/40