Fix panic in merge join when using custom Indexes that don't allow range lookups. #1985
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
…nge lookups. (For instance, dolt has Commit indexes for tables that use commit hash as an index, but ranges don't make sense for those.) There's no equivalent in GMS, so I created "point_lookup_table" table function for use in tests.
max-hoffman
approved these changes
Sep 5, 2023
…. This is less error-prone than returning a null pointer on failure.
…'t be used for range lookups.
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.
For instance, dolt has Commit indexes for tables that use commit hash as an index, but ranges don't make sense for those.
There's no equivalent in GMS, so I created "point_lookup_table" table function for use in tests.