tursodatabase / tursodatabase/libsql-js
Read-only transaction support
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- JavaScript
- Stars
- 335
- Forks
- 48
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 3
Description
The libSQL crate now supports BEGIN READ ONLY (https://github.com/tursodatabase/libsql/commit/91f4780c0b5eeb738c10abd82d1d8a97e99b2923), let's wire it up in the transaction API.
Contributor guide
No contributing guide indexed for this repository
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 at the transaction API and inspect how transaction modes are represented and translated into SQL. Compare that path with the linked libSQL commit supporting BEGIN READ ONLY, then verify that the API can request a read-only transaction and that the resulting transaction behavior is covered by the relevant existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, sqlite
- Domain
- api, database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100