-
-
Notifications
You must be signed in to change notification settings - Fork 873
Duckdb: Adding InsertStatementSegment for Duckdb specifics #6740
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
Duckdb: Adding InsertStatementSegment for Duckdb specifics #6740
Conversation
Coverage Results ✅
|
Ref("WithNoSchemaBindingClauseSegment"), | ||
Ref("WithDataClauseSegment"), | ||
Sequence("ON", "CONFLICT"), | ||
Ref.keyword("RETURNING"), |
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.
Ref.keyword("RETURNING"), | |
"RETURNING" |
You can specify keywords directly as strings if no options are needed
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.
Ok, good to know, thanks. I'll update it.
FYI, I copied that part from:
Ref.keyword("RETURNING"), |
@@ -484,6 +548,8 @@ class UnorderedSelectStatementSegment(ansi.UnorderedSelectStatementSegment): | |||
Ref("SetOperatorSegment"), | |||
Ref("OrderByClauseSegment"), | |||
Ref("LimitClauseSegment"), | |||
Sequence("ON", "CONFLICT"), | |||
Ref.keyword("RETURNING"), |
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.
Ref.keyword("RETURNING"), | |
"RETURNING", |
5f6d147
to
e63062d
Compare
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.
LGTM
Brief summary of the change made
Fixes #6649
Adding the InsertStatementSegment for Duckdb specific syntax following documentation:
https://duckdb.org/docs/stable/sql/statements/insert.html
Are there any other side effects of this change that we should be aware of?
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 withtox -e generate-fixture-yml
).test/fixtures/linter/autofix
.Added appropriate documentation for the change.
Created GitHub issues for any relevant followup/future enhancements if appropriate.