sql.js size optimization
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Not exactly a issue, more of a question/idea. I'm trying for a serverless application, and I need to run a few complex queries (tree-like and such). The data would be imported from another source on load time and there would be no need to maintain it, just query. In the end, I would need a sql.js that could:
- create tables (no need to alter/drop);
- insert data (no need to update/delete);
- run complex query on low volume data (few thousand lines at most - no need for views, but temp tables, indexes and subqueries needed).
Do you know if these are achievable on compile time? And would you consider making a sql.js version with such features? If possible, I imagine this could shrink the sql.js a lot.
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
The issue names no files, tests, or entry points. First determine whether sql.js/SQLite features can be excluded at compile time while retaining table creation, inserts, indexes, temporary tables, subqueries, and complex queries. Done would include a measured smaller build and confirmation that the requested operations still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, sqlite, wasm
- Domain
- build-system, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100