tursodatabase / tursodatabase/libsql-js
Support readonly option
Open
Nobody has claimed this yet.
api compat
good first issue
help wanted
- Dominant language
- JavaScript
- Stars
- 335
- Forks
- 48
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 3
Description
With better-sqlite3, the readonly option behaves as such:
- Constructor fails when combined with an in-memory database
TypeError: In-memory/temporary databases cannot be readonly
- Queries that mutate fail
SqliteError: attempt to write a readonly database
db.readonlyset to true
This library does none of the above yet.
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
Compare the library's connection-option entry point and existing tests with better-sqlite3's readonly behavior. Done means the readonly option rejects in-memory databases, prevents mutating queries, and exposes a true db.readonly value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, sqlite
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100