IDBFS persistent backend example
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
As far as I understand sql.js no longer needs to export the whole database to persist data with this new backend!!!
https://github.com/kripken/emscripten/blob/master/src/library_idbfs.js
http://kripken.github.io/emscripten-site/docs/api_reference/Filesystem-API.html#filesystem-api-idbfs
We should add an example that sets up sql.js with IDBFS chosen, and then compare performance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Emscripten library_idbfs.js source and Filesystem API documentation, then inspect sql.js's existing example structure. Add an example configuring sql.js with IDBFS persistence and include a performance comparison; done means the example works and the comparison is reported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, sqlite
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100