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

I have a slow page in my app due to a full table scan to check a boolean field (looking for true values, where ~1% of values are true).

My options are:

1. Do nothing, let it be slow.
2. Switch from true/false to 1/0 - is that actually a problem? Kind of. It's a very slow upgrade, since I need to read every single object in the store into memory, and there are a lot of them, and they are large. Bad UX.
3. Complain here :)

I feel like any argument against supporting booleans here is not valid unless it would also be made against supporting booleans in JavaScript in general. Because they're desired here for the same reasons they are desired anywhere.

But I understand, we can't go back in time and add it to the initial spec. Instead, we need people to spend a non-trivial amount of time to add this tiny little feature that most people will never notice. And I know you all have more important stuff to do. But if I've earned myself any goodwill in the community by [writing an IndexedDB library used in thousands of projects, including some made by the major browser vendors](https://github.com/dumbmatter/fakeIndexedDB)... please do something about this issue :)

-- 
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-922418845