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

@jfroelich That fits more with #45. It's not a crazy thought, but the devil is in the details:

Arbitrary JS is not a win over the existing cursor mechanism. There's always room for improvement in implementations, but that's a "quality of implementation" thing. There's the notion of lightweight stateless isolated computation environments - [Worklets](https://drafts.css-houdini.org/worklets/) are the new hotness here. But even then you're paying for some overhear. In Chrome, for example, we don't run JS in the process that touches the database, so we would still have the IPC overhead. Also, database entries require deserialization before JS can see them.

So all of this turns into "is there a domain-specific language we could use to express queries that is executed directly in the database engine?" - whether it looks like a subset of JS or is a declarative structure (which is what e.g. ranges or sets a simple cases of) is what needs consideration and designing. Again, this is what #45 is pointing towards.

So not naive, but not simple.

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