fix(jdbc-v2): Correctly parse mixed-order CTEs in SqlParser #2611
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.
Summary
The grammar for CTEs was too restrictive. It required a specific order for different CTE syntax styles.
The grammar expected all CTEs to be defined before all CSEs (Common Scalar Expression).
This commit refactors the
ctesgrammar rule to be more flexible. It introduces a new, more genericcterule that can represent either CTE style. The mainctesrule is now defined as a list of these genericcteelements, allowing them to appear in any order.Checklist
Delete items not relevant to your PR: