Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Does duckdb-wasm support local persistency of data in browser #872

Closed
hi-sunshine opened this issue Jul 5, 2022 · 3 comments
Closed

Does duckdb-wasm support local persistency of data in browser #872

hi-sunshine opened this issue Jul 5, 2022 · 3 comments

Comments

@hi-sunshine
Copy link

Does duckdb-wasm support local persistency of data in browser ? if not, is there any plan to support it ? thanks!
@ankoh
Copy link
Member

ankoh commented Jul 5, 2022 •
edited
Loading

We cannot support local persistency today since browsers insufficiently support blocking I/O.
But we're planning to support local persistency once this lands: whatwg/fs#7 (comment)

@ankoh ankoh closed this as completed Jul 11, 2022
@goenning
Copy link

Hi @ankoh seems like the above proposal already landed on some browsers. Is it possible to do local persistency as of today? My plan was to store parquet files on indexed DB and load them into duckdb on PageLoad, is there a better way of doing this?

@derekperkins
Copy link

For reference, this is being worked on here:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@goenning @derekperkins @ankoh @hi-sunshine