Change output name of CAST expressions #3328
Closed
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
andygrove
force-pushed
the
cast-physical-name
branch
from
4321912
to
c612c26
Compare
andygrove
force-pushed
the
cast-physical-name
branch
from
280c24e
to
9b580e9
Compare
andygrove
changed the title
andygrove
changed the title
24 tasks
|
This is turning out to be more complex and nuanced than I had realized. |
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.
Which issue does this PR close?
Closes #3326
Rationale for this change
Match Postgres and Spark behavior, where a CAST does not rename an expression
What changes are included in this PR?
Change physical name of CAST
Are there any user-facing changes?
No