-
-
Notifications
You must be signed in to change notification settings - Fork 873
Clickhouse: support more complex types and functions in table definition #6804
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
Clickhouse: support more complex types and functions in table definition #6804
Conversation
9a96933
to
f1dfdb0
Compare
Coverage Results ✅
|
Sequence( | ||
StringParser("NULLABLE", CodeSegment, type="data_type_identifier"), | ||
StringParser("Nullable", CodeSegment, type="data_type_identifier"), |
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.
Our pattern generally for StringParser() is to uppercase the contents. Can you change your ones to match this?
Sequence( | ||
StringParser("NULLABLE", CodeSegment, type="data_type_identifier"), | ||
Bracketed(Ref("DatatypeSegment")), | ||
), | ||
# LowCardinality(Type) | ||
Sequence( | ||
StringParser("LowCardinality", CodeSegment, type="data_type_identifier"), |
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.
Theres abunch more - like here, can you fix them all?
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.
I think now I did. I had not used all caps because clickhouse is quite sensitive to the casing and does not accept all caps for data types.
Co-authored-by: Danny Jones <51742311+WittierDinosaur@users.noreply.github.com>
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
Adds support
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.