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
Grammar: Adds support for ALTER VIEW statement for Postgres dialect #2096
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2096 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 148 148
Lines 10603 10608 +5
=========================================
+ Hits 10603 10608 +5
Continue to review full report at Codecov.
|
Sequence( | ||
"SET", | ||
"DEFAULT", | ||
OneOf( | ||
Ref("LiteralGrammar"), | ||
Ref("FunctionSegment"), | ||
Ref("BareFunctionSegment"), | ||
Ref("ExpressionSegment"), | ||
), | ||
), |
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.
You're correct here. I noticed that the existing AlterTableActionSegment only allows expression segments when it should also account for the segments you have here. If you're interested would you be able to create a separate PR to match that line to the SET DEFAULT grammar you have here and add the corresponding unit tests? 😄
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.
Raised here: #2101
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.
@derickl Fantastic work, looks perfect to me! 🚀
P.S. see my note from the review for a quick future PR suggestion
Brief summary of the change made
Adds support for parsing
ALTER VIEW
statements for the Postgres dialectCloses #2094
Are there any other side effects of this change that we should be aware of?
None
Pull Request checklist
Please confirm you have completed any of the necessary steps below.
Included test cases to demonstrate any code changes, which may be one or more of the following:
.yml
rule test cases intest/fixtures/rules/std_rule_cases
..sql
/.yml
parser test cases intest/fixtures/dialects
(note YML files can be auto generated withpython test/generate_parse_fixture_yml.py
or by runningtox
locally).test/fixtures/linter/autofix
.Added appropriate documentation for the change.
Created GitHub issues for any relevant followup/future enhancements if appropriate.