-
Notifications
You must be signed in to change notification settings - Fork 0
Bigquery col alias override #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
ec9739f
to
8dedb1b
Compare
@goldmedal Thank you for the review. I have addressed your comments. I agree that encoding the column name is a better idea. Also, I will add a test case that includes a special character column name in the where clause. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @douenergy. looks good to me 👍
I leave some minor suggestions.
Thanks @douenergy |
Which issue does this PR close?
Canner/wren-engine#1089
Rationale for this change
Add an additional unparser rule for every dialect to allow dialects to override column aliases.
What changes are included in this PR?
Rewrite BigQuery column aliases.
Are these changes tested?
In datafusion/sql/tests/cases/plan_to_sql.rs
roundtrip_statement_with_dialect
.