Suggested way to persist a database across browser refreshes in wasm

[david542542]

Take the following scenario using duckdb-wasm within a browser:

1. A user creates a table, such as from a csv file (CREATE TABLE tbl AS SELECT * FROM 'myfile').
2. A user performs a modification to the table (ex DELETE FROM tbl WHERE id < 10).
3. A user now refreshes the page.

We want to be able to reload the table that the user had just been prior to refreshing the page. We can write a parquet file using something like https://wicg.github.io/file-system-access/. However, what should be done about the additional data modifications after the first initial import? Ideally we'd like to have a concept similar to an initial base db + a WAL or something (rather than having to re-save the parquet file after each modification, which, depending on the size of the table, could take a long time).

What would you suggest to do here to accomplish this?