[Feature Request] Support for sqlite3_interrupt
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Hey sql.js maintainers! Thanks so much for this great software, we've been getting great milage out of it!
It sounds like it's possible to add sqlite3_interrupt support based on your discussion in #461, it just hasn't been prioritized. We've implemented the suggested workaround of killing and re-instantiating the worker, but obviously it would be a lot more performant if we surgically interrupted queries.
Is this feature on your radar? Any idea of how much work it would involve? Thanks in advance!
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
Read the discussion in #461 and inspect how sql.js currently runs queries in its worker, including the workaround of killing and recreating that worker. Define how sqlite3_interrupt should be exposed and verify that an in-progress query can be interrupted without restarting the worker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, sqlite, wasm
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100