Fix TS composite btree range scans#5479
Open
JasonAtClockwork wants to merge 3 commits into
Open
Conversation
This file contains hidden or 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
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.
Description of Changes
Closes #5454
Fixes TypeScript modules for indexes
filter()anddelete()methods where the final provided argument is aRange.filter()anddelete()to choose between point scans and ranged scansserializeRangeso range bounds are sliced after the prefix instead of the startAPI and ABI breaking changes
No breaking changes this is a bug fix
Expected complexity level and risk
2 - Limited change to the index logic for
filter()anddelete()Testing
filter()anddelete()with a composite key ending inRange