Vector35 / Vector35/binaryninja-api
Compression support for databases
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Some databases takes much space that's why having an option for compressing databases would be useful. It also useful for sharing databases with others. In the near future, I predict that the size of databases could grow quite large when support for multi-binary databases and projects comes into play, so it will be useful there too.
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 names no files, tests, or entry points. First clarify which database formats and compression workflows are required, including storage and sharing expectations; then identify the relevant database handling entry points and define completion criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100