Re: [w3c/IndexedDB] Custom index keys (#204)

Regarding the API, we'd need to distinguish multiple keys from compound keys. e.g. in the `store.put(record, undefined, {fulltext: terms});` case, `terms` is presumably an array `["lorem", "ipsum", ...]` and we want one index entry for each array entry, not a single entry with a compound key. That could be done automagically via the `multiEntry` flag for the index (i.e. exactly the same way that the index key is interpreted when not using a map), but that may be too subtle.



-- 
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/204#issuecomment-315872697

Received on Monday, 17 July 2017 20:27:15 UTC