tursodatabase / tursodatabase/libsql
libsql crate: allow passing multiple statements with bound parameters to execute_batch
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Our execute_batch api currently takes a single SQL string, following rusqlite convention. We would also want to be able to send multiple statements with bound parameters in a single batch, without flattening them to a single string.
Example from libsql-client-rs:
https://github.com/libsql/libsql-client-rs/blob/b92e67bcc11f0820cbc66ecc8c6b3286bf726111/examples/select.rs#L51-L65
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 reading the libsql crate's execute_batch API and the linked libsql-client-rs examples/select.rs lines 51-65. Trace how statements and bound parameters are currently passed, then define the batch behavior and verify that multiple parameterized statements can be executed without flattening them into one SQL string.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sqlite
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100