feature-request - add appendFile-like capability to overcome nedb performance-bottleneck about kv-storage HOT 4 CLOSED

I'm not quite sure I understand this. In particular, what IndexedDB operations do you suggest this maps to?

from kv-storage.

there is no existing IndexedDB operation to "append" data to an entry. this would be a new operation in kv-storage, for example:

// persist nedb as logfile
tx.objectStore(store).add("nedb", "");
// log set-operation to table1
tx.objectStore(store).append("nedb", 'table1 set { "id": 1, "field1": "foo", "field2": "bar" }\n');
// log set-operation to table1
tx.objectStore(store).append("nedb", 'table1 set { "id": 2, "field1": "baz", "field2": "quz" }\n');
// log delete-operation to table1
tx.objectStore(store).append("nedb", 'table1 delete { "id": 1 }\n');

...

// restart browser, and restore nedb by replaying logfile
var logfile = tx.objectStore(store).get("nedb");
var myDb = replay(logfile);
// myDb = { table1: [{id: 2, field1: "baz", field2: "qux"}] }

because IndexedDB has no append feature, nedb currently has to inefficiently set the entire logfile for write-persists.

from kv-storage.

Ah, OK. Since KV Storage is just a higher-level interface on top of IndexedDB, I think you'd be best off opening the issue on the IndexedDB specification instead: https://github.com/w3c/IndexedDB/issues/. It's not within scope here to add things which are impossible to accomplish with IndexedDB.

Closing, but happy to continue discussing in the closed thread!

from kv-storage.

ok, thx for clarifying scope of kv-storage as just mapping of indexeddb.

from kv-storage.