- From: Victor Costan <notifications@github.com>
- Date: Sat, 18 Jul 2020 20:16:47 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Sunday, 19 July 2020 03:16:59 UTC
@kaizhu256 How about filing a bug at https://crbug.com/new explaining your situation? I'm curious to learn why you need large *keys*. Starting in Chrome 84, we've significantly improved how we handle large *values*. Based on what I know about databases used as backing stores for IndexedDB, I'm hoping to drive the web ecosystem towards *small keys*, where "small" means at most kilobytes in length. This is because keys show up in indexes, and key length directly impacts the performance of all database operations. -- 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/344#issuecomment-660578854
Received on Sunday, 19 July 2020 03:16:59 UTC