Re: [w3c/IndexedDB] Introduce a more general query mechanism beyond keys/ranges (#45)

If there's no index on a property then this involves decoding every record, which (at least in Chrome) is a process hop and likely jank, akin to creating a new index on existing store. While that's a "quality of implementation" thing I wonder if that'll be common across browsers.

It also might be incentive to create/maintain automatic indexes; you'd pay the cost on the first query. (I bet there's a fancy database term for that.)


-- 
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/45#issuecomment-248889264