tursodatabase / tursodatabase/libsql
Exclusive access mode for local writes?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Allowing local writes with the libSQL library is convenient for many use cases. The single-writer scheme is great for simplicity, and we want to keep that. One possible way to allow local writes is to let a client request exclusive access to a database (much like CPU caches do). Of course, there's always the failure condition where a library never releases the database, but we can add controls to the libSQL server for operators to force the server to become the owner.
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, tests, or entry points. Start by mapping how libSQL coordinates the single writer between clients and the server, then identify the ownership and forced-release paths that would need a design. Done would require an agreed protocol, failure handling, and tests for exclusive access and server takeover.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100