Expose an interface to sqlite3_file_control
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Feature or enhancement
Proposal:
sqlite3_file_control can affect the semantics of a sqlite3 database, but is not exposed by the sqlite.Connection class. In particular, I would like to use the SQLITE_FCNTL_PERSIST_WAL opcode, which ensures that callers can open a WAL-mode database on a read-only mount even when the writers have closed the DB.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response
Linked PRs
- gh-128507
- gh-148870
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 reading the sqlite3.Connection interface and the sqlite3_file_control documentation, then review linked PRs gh-128507 and gh-148870 for the current implementation direction. Done means the requested file-control capability is exposed through the connection interface and supports the SQLITE_FCNTL_PERSIST_WAL use case described here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100