Re: [w3c/IndexedDB] Support queries retrieving disjoint sets of keys (#19)

Rebooting, and referencing https://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0848.html which emphasizes the benefits of lists over sets:

```webidl
[Constructor(sequence<any>), Exposed=(Window,Worker)]
interface IDBKeyList {
  iterable<any>;
};
```

Anywhere in the spec that takes `any query` as an argument would be augmented to allow an IDBKeyList in addition to keys and IDBKeyRange. This includes: get(), getKey(), getAll(), getAllKeys(), count(), openCursor(), openKeyCursor() and delete(). This would be done by changing [convert a value to a key range](https://w3c.github.io/IndexedDB/#convert-a-value-to-a-key-range) to "convert a value to a query". A _query_ gets a definition like a _key range_ where keys can be _in a query_. 

The database operations (retrieval, delete, count) change to taking a _query_. 

Cursor iteration is more intrusive. Maybe we disallow?



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/19#issuecomment-502299229