fix: fetch data by prefix will get more data than needed #71
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
blckngm
reviewed
Sep 15, 2023
wenyuanhust
changed the title
KaoImin
approved these changes
Sep 15, 2023
KaoImin
changed the title
blckngm
approved these changes
Sep 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The IteratorMode::From mode starts the iterator at the first key that is greater than or equal to the provided key.
rust-rocksdb/rust-rocksdb#370
If there are keys that sort after your prefix but are not part of it, they will still be included in the iteration.
https://bleepcoder.com/rust-rocksdb/378811240/the-prefix-iterator-behaves-weirdly