tursodatabase / tursodatabase/libsql
Sync does not handle existing database correctly
Open
Nobody has claimed this yet.
bug
Embedded Replicas
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
Steps to reproduce:
- Create a local
hello.db - Import the database with https://turso.tech/blog/migrating-and-importing-sqlite-to-turso-just-got-easier
- Sync the database
Expected results:
- Sync fails to overwrite an existing database with no metadata
Current results:
- Sync succeeds.
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 steps with a local hello.db: create it, import it using the linked Turso migration guidance, and run Sync. Trace the Sync entry point for an existing database with no metadata; done means Sync no longer succeeds in that case and the expected failure is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100