- From: Victor Costan <notifications@github.com>
- Date: Thu, 28 Mar 2019 07:59:16 +0000 (UTC)
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 28 March 2019 07:59:39 UTC
Typical databases have some sort of block cache, and need to write modified blocks to disk. The sub-system is sometimes called the page cache or the pager. If nedb has something similar, it should use a Blob for each block / size, instead of writing the entire database in a single Blob. Each block would be a Blob in an object store keyed by block ID. You can use this approach to build a database or a filesystem on top of IndexedDB. There's still overhead, but at least it's constant, not O(database size). If you need something working soon, the approach above should give you some relief until we're able to build and ship the future APIs mentioned by @inexorabletash. I hope this helps! -- 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/260#issuecomment-477488844
Received on Thursday, 28 March 2019 07:59:39 UTC