tursodatabase / tursodatabase/libsql
Handling writes with file-based sync?
Open
Nobody has claimed this yet.
enhancement
question
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
The current model is that writes are always delegated to the primary, but it's unclear how that will work when file-based sync is used.
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 locating the file-based sync implementation and the code that delegates writes to the primary, then determine the expected write behavior and document a concrete acceptance case for it.
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
- 20/100