Uh oh!
There was an error while loading. Please reload this page.
chore(deps): Update sqlparser to 0.54.0 - #14255
Conversation
Uh oh!
There was an error while loading. Please reload this page.
| ---- | ||
| 5.000000000 secs | ||
| 60 mons |
There was a problem hiding this comment.
this certainly seems much more correct to me -- I also removed the now out of date comment.
| } | ||
| fn sql_subscript_to_expr( | ||
| fn sql_compound_field_access_to_expr( |
There was a problem hiding this comment.
The code to plan CompoundFieldAccess is directly copy/pasted from @goldmedal 's PR
0.54.0| /// | ||
| /// For example, `foo.bar` would be represented as a two element vector | ||
| /// `["foo", "bar"]` | ||
| fn from_idents(mut idents: Vec<String>) -> Option<Self> { |
There was a problem hiding this comment.
Changed the signature to be easier to work with (pass the vec by ownership rather than &mut)
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| # left_join_using_qualified (snowflake syntax) | ||
| query error DataFusion error: This feature is not implemented: Invalid identifier in USING clause\. Expected single identifier, got t2\.c2 | ||
| SELECT t1.c1, t2.c2 FROM test_partition_table t1 JOIN test_partition_table t2 USING (t2.c2) ORDER BY t2.c2; |
goldmedal
commented
Feb 5, 2025
@alamb There are some conflicts here. |
Co-authored-by: Jax Liu <liugs963@gmail.com>
… into alamb/upgrade_sqlparser
alamb
commented
Feb 5, 2025
Thank you for the review @goldmedal -- I have merged up and resolved the conflicts |
goldmedal
commented
Feb 5, 2025
🚀 |
alamb
commented
May 21, 2025
This appears to have caused a regression: |
Which issue does this PR close?
Rationale for this change
Keep up with latest SQL parser dependencies
What changes are included in this PR?
Are these changes tested?
Yes by CI
Are there any user-facing changes?