tursodatabase / tursodatabase/libsql-js
A `better-sqlite3` process writes to database but another `libsql` process does not see them
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 335
- Forks
- 48
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 3
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
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 body contains no reproduction, files, tests, or environment details. Start by creating a minimal two-process reproduction using the better-sqlite3-compatible and libSQL APIs described in the title, then determine when writes become visible across processes. Done means the visibility behavior is understood and the issue has a reproducible test or clearly documented limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, sqlite
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100