Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature Request] Support for sqlite3_interrupt

Open
#545 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, sqlite, wasm
Domain
databases

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.

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!

Dominant language
JavaScript
Stars
13.7k
Forks
1.1k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sql-js/sql.js

All issues in sql-js/sql.js

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.