tursodatabase / tursodatabase/libsql
Either support or reject BEGIN READONLY in hrana on the server
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Right now it does nothing and allows write transactions:
→ delete from test;
→ select * from test;
A
→ begin readonly; insert into test values(101); select * from test; commit;select * from test;
A
101
A
101
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 reproducing the shown BEGIN READONLY transaction in the hrana server and trace how the server handles transaction modes. Determine whether the intended result is to enforce read-only behavior or reject the syntax, then add coverage proving that writes cannot proceed silently and run the relevant server tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100