[Feature Request] Support for sqlite3_interrupt
还没有人认领这个 Issue。
- 主要语言
- JavaScript
- 星标
- 13.7k
- 派生
- 1.1k
- PR 合并指标
- 30 天内没有已合并 PR
描述
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!
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
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.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- javascript, sqlite, wasm
- 领域
- databases
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100