fix: unnest join constraint with alias parsing for BigQuery dialect #732
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.
This PR fixes a parsing bug for the BigQuery Dialect.
The expected outcome is for the following statement to be parsed with join constraints:
However, this statement would result in the following error:
Closer inspection revealed that the following ast was produced for the join table factor
As you can see, the
with_offset_alias
parses theON
keyword despite thewith_offset
being false.To replicate this behaviour, I added a failing test that verifies this behaviour difference
This fix uses the boolean check to determine if the subsequent optional alias should be parsed.