Clarification on SQLite support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 35
- Forks
- 34
- Avg merge
- 5h 46m
- Merged PRs (30d)
- 12
Description
cc @ldionne
I see there's been a bunch of activity on moving tests to postgres e.g. https://github.com/llvm/llvm-lnt/pull/197, I think that's fine, and I agree it's better to run these tests on what production servers will run.
But I just want to confirm that we're not removing SQLite support itself? Having the ability to spin up an instance locally without installing postgres is a workflow that myself and a few of my colleagues are currently using. It's handy to view benchmark runs locally.
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
Start by reading the linked PR 197 and reviewing how the project currently runs tests against PostgreSQL and SQLite. No specific file or test is named; done would be a clear project decision or documentation stating whether local SQLite support remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlite
- Domain
- databases
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100