Use fully qualified names in ORDER BY clause. #1080
Closed
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
mp911de
reviewed
Nov 8, 2021
| @@ -77,7 +77,7 @@ Delegation leaveMatched(OrderByField segment) { | |||
| Delegation leaveNested(Visitable segment) { | |||
|
|
|||
| if (segment instanceof Column) { | |||
| builder.append(NameRenderer.reference(context, (Column) segment)); | |||
| builder.append(NameRenderer.fullyQualifiedReference(context, (Column) segment)); | |||
There was a problem hiding this comment.
Shouldn't this consider aliased column names as we want to order by a specific thing that is being selected (SELECT foo.bar as fb, baz.bar as foo.bar … ORDER BY fb)?
|
That's merged and polished now. |
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.
Closes #968