tursodatabase / tursodatabase/libsql
Query cancellation support
Open
Nobody has claimed this yet.
enhancement
good first issue
help wanted
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Let's expose sqlite3_interrupt() in the libsql API for both synchronous and asynchronous execution.
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
Start by locating the libsql API entry points for synchronous and asynchronous query execution, then trace how SQLite functions are exposed. Use sqlite3_interrupt() as the requested interface and verify that cancellation is available through both execution paths; the issue provides no specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- api, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100