Suggested way to persist a database across browser refreshes in wasm #1441
Unanswered
david542542
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Take the following scenario using
duckdb-wasm
within a browser:CREATE TABLE tbl AS SELECT * FROM 'myfile'
).DELETE FROM tbl WHERE id < 10
).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?
Beta Was this translation helpful? Give feedback.
All reactions