[Wallet] remove unused code/conditions in ReadAtCursor #8564
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Long term goal should be to provide alternative database connectors for our wallet. I have worked out a flexible adaptor like pattern that would allow a drop-in-alternative/replacement for BDB (https://github.com/jonasschnelli/bitcoin/tree/2016/08/bdb_abstract_prework).
This is a small, easy-to-review trivial PR towards this direction.
CDB::ReadAtCursor()has some unused flags handling (which would be relative hard to abstract for other databases). It seems like it only used to set a filter for the key (DB_SET_RANGE).This removes unused code and simplifies
CDB::ReadAtCursor()logic.