expression: the quote function should treat null expr as NULL literal string instead of NULL (#11592) #13681
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
zz-jason
approved these changes
Nov 25, 2019
zz-jason
added
status/LGT2
…upstream-release-2.1
|
/run-all-tests |
|
@SunRunAway merge failed. |
|
/run-unit-test |
SunRunAway
deleted the
automated-cherry-pick-of-#11592-upstream-release-2.1
branch
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.
Automated cherry pick of #11592 on release-2.1.
What problem does this PR solve?
Fix #11556 QUOTE(null) should return 'NULL' string instead of NULL value
What is changed and how it works?
if the expr is NULL, then the value for quote(expr) will be "NULL" instead of NULL.
Check List
Tests
Side effects