tursodatabase / tursodatabase/libsql
step()-based API support in libSQL
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
The libSQL core API follows rusqlite's API but it means language bindings such as JavaScript one has to do work around the rusqlite API to be compatible with better-sqlite3. Let's add a bind() + step() based API in the libSQL core, perhaps even making the rusqlite compatibility API a separate crate.
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
The issue names no files or tests; start by reviewing the libSQL core API and its rusqlite compatibility API, then compare the needs of JavaScript bindings such as better-sqlite3. The work is complete only after the bind()/step() API scope and the compatibility-crate split are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust, sqlite
- Domain
- api, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100