Fix(snowflake): parse CREATE SEQUENCE with commas #3436
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.
Fixes #3435
Note that the two DDLs tested produce slightly different ASTs:
This happens because when we only have
KEY=VALUE
pairs separated by whitespace we don't ever reach_parse_sequence_properties
, but when there's a comma we do reach it and so theSequenceProperties
is produced. It's not 100% clean but not sure if a refactor is high ROI right now to make the two ASTs match.