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
Snowflake: Support CURRENT_TIMESTAMP as a column default value #1578
Snowflake: Support CURRENT_TIMESTAMP as a column default value #1578
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1578 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 131 131
Lines 9172 9172
=========================================
Hits 9172 9172
Continue to review full report at Codecov.
|
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.
Change looks great!
One comment to consider taking this to the next level.
d178bb2
to
ba9ded1
Compare
Looks great. If you could just run |
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.
Approved, with a small formatting change I'll commit.
The DBT errors are something we introduced so ignore them.
Thanks for the contribution! Will be included in next release.
e19bd27
to
ef8cba6
Compare
…uff#1578) * Column default value: Support CURRENT_TIMESTAMP Issue sqlfluff#1576 * * Generated `yml` fixture * * Added `SYSDATE()` and `CURRENT_TIMESTAMP` optional precision support * Update src/sqlfluff/dialects/dialect_snowflake.py Co-authored-by: Barry Pollard <barry_pollard@hotmail.com> Co-authored-by: Barry Pollard <barry@tunetheweb.com>
Brief summary of the change made
CURRENT_TIMESTAMP
as a column default value in Snowflake dialect.Fixes #1576
Are there any other side effects of this change that we should be aware of?
Not that I'm 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:
.sql
/.yml
parser test cases intest/fixtures/parser
(note YML files can be auto generated withpython test/generate_parse_fixture_yml.py
or by runningtox
locally).