Implement unparse OuterReferenceColumn
to String
#10544
Merged
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 #10523
Rationale for this change
IMO,
OuterReferenceColumn
is a column can be resolved to an outside field of the current plan. Typically, it's produced fromidentifier
orcompound_identifier
.datafusion/datafusion/sql/src/expr/identifier.rs
Lines 64 to 69 in 7535d93
I think we can just convert it to a
column
sql node. Just like other identifier. Because the concept ofouter reference
is a logical plan concept, we can ignore the type of aOuterReferenceColumn
which produced by a field resolving.What changes are included in this PR?
Convert
OuterReferenceColumn
to a Column SQL node.Are these changes tested?
Yes
Are there any user-facing changes?
No