tursodatabase / tursodatabase/libsql
Rows written with `INSERT OR IGNORE` still read/writing
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
I am frequently inserting datasets with many duplicates using INSERT OR IGNORE ....
However, it appears that this still causes writes (and also maybe reads?) on the remote replicant?
Is this expected behavior? Is there a configuration to prevent this?
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
No files, tests, or entry points are named. Start by reproducing the INSERT OR IGNORE workload against a remote replicant and inspect whether ignored rows generate reads or writes. Done means confirming the behavior and documenting the relevant configuration or expected limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100