INCATools / INCATools/semantic-sql
Evaluate sqlite-zstd compression as alternative to gzip
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 69
- Forks
- 7
- Avg merge
- 8m
- Merged PRs (30d)
- 1
Description
semantic-sql currently uses simple gzip compression. This is generally OK: it's universally recognized, most environments have the tools to decompress it, and provides a good lossless compression ratio.
For sqlite in particular, an alternative compression strategy like `sqlite-zstd` can provide similar compression ratios or better while supporting the usual CRUD operations without needing to decompress the whole database file.
See https://crates.io/crates/sqlite-zstd
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 locating semantic-sql's current gzip compression path and SQLite database handling, then review sqlite-zstd's documented CRUD capabilities. The issue names no files, tests, or acceptance criterion, so completion would require defining the comparison scope and recording a recommendation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100