Re: [w3c/IndexedDB] boolean should be a valid key (#76)

I'd be interested in a reply on my [earlier comment](https://github.com/w3c/IndexedDB/issues/76#issuecomment-296501281l).

It would seem to me to be of much greater convenience to users if they wouldn't need to refactor, at least when using simple types like booleans (or `undefined` or `null`), if moving to IndexedDB or using kv-store. I'd imagine booleans are pretty common in local storage. (A kv-store example uses them here: https://wicg.github.io/kv-storage/#example-backingstore ; it may come as an unwelcome surprise that one can't take advantage of the "indexed" nature behind data so stored even after obtaining the backing store.)

This and `IdentifierName` restrictions seem to discourage taking advantage of indexes on common data store structures, e.g., those originally as JSON, and data that might not be possible or desirable to change at the source or incur the cost of transforming to (and possibly from) numeric values.

Imho, it would facilitate more indexing if consumers wouldn't need to reshape their data so as to gain the ability to add indexes.

-- 
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/76#issuecomment-502890201