[Feature Request] Support for sqlite3_interrupt

未關閉
#545 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
javascript, sqlite, wasm
領域
databases

研究方向

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 內容生成。

描述

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!

主要語言
JavaScript
星號
13.7k
分支
1.1k
PR 合併指標
30 天內沒有已合併 PR

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

sql-js/sql.js 的其他 Issue

查看 sql-js/sql.js 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。