Fix: handle NULL input for regex match operations#12028
Merged
alamb merged 1 commit intoapache:mainfrom Aug 17, 2024
Merged
Conversation
github-actions
Bot
added
physical-expr
alamb
approved these changes
Aug 16, 2024
Contributor
alamb
left a comment
alamb
left a comment
There was a problem hiding this comment.
Thanks @HuSen8891 🙏
cc @2010YOUY01 the sqlancer project keeps paying off
Contributor
|
Thanks again @HuSen8891 |
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
2 participants
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.
Which issue does this PR close?
Closes #11623
Rationale for this change
For regex match operations, handle NULL input, such as
select v1 ~ null from t; --- described in #11623
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?