Vector35 / Vector35/binaryninja-api
Incremental database saving
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
What is the feature you'd like to have?
Now, databases saves entirely even I did small change in them. And for large binaries it took 2-5 minutes. It would great if there's way somehow optimize saving only parts that actually changed.
Example
In my project I changed uint64_t to uint32_t for one variable in function, but saving still did for 3 minutes.
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 identifies no file, test, or entry point to read or run first. It requests incremental saving of only changed database portions, so the scope and completion criteria would need to be defined before implementation and performance validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100