tursodatabase / tursodatabase/libsql
Desired features exposed in C bindings
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
There are a few features that would be nice to expose in the C bindings for client development. The list can grow but as of now these are the features I want to implement in a client library.
- Database::open_remote
- Connection::changes
- Connection::last_insert_row_id
- Connection::query
- Specifically with params (both positional and named) (currently stubbed)
There are several others but these should be enough to get a mostly useful client library running.
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 in bindings/c/src/lib.rs, especially the currently stubbed query binding, and compare it with the linked Rust Database and Connection APIs. Done means exposing open_remote, changes, last_insert_row_id, and query with both positional and named parameters so a mostly useful client library can use them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust, sqlite
- Domain
- api, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100