Skip to content
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

Add handling for Redshift CONVERT function data type argument #3653

Merged
merged 1 commit into from Jul 23, 2022

Conversation

pdebelak
Copy link
Contributor

Brief summary of the change made

Fixes issue #3651.

Previously, the first argument to the convert redshift function was interpreted as a column reference rather than a data type. This could cause rule L027 to fail since the data type wasn't qualified with a table name even though that doesn't make sense. This adds explicit handling for convert to eliminate that issue.

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:

    • .yml rule test cases in test/fixtures/rules/std_rule_cases.
    • .sql/.yml parser test cases in test/fixtures/dialects (note YML files can be auto generated with tox -e generate-fixture-yml).
    • Full autofix test cases in test/fixtures/linter/autofix.
    • Other.
  • Added appropriate documentation for the change.

  • Created GitHub issues for any relevant followup/future enhancements if appropriate.

@codecov
Copy link

codecov bot commented Jul 22, 2022

Codecov Report

Merging #3653 (011e195) into main (8e4f29e) will not change coverage.
The diff coverage is n/a.

❗ Current head 011e195 differs from pull request most recent head a29aa51. Consider uploading reports for the commit a29aa51 to get more accurate results

@@            Coverage Diff            @@
##              main     #3653   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          176       176           
  Lines        13328     13326    -2     
=========================================
- Hits         13328     13326    -2     
Impacted Files Coverage Δ
src/sqlfluff/core/linter/linter.py 100.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8e4f29e...a29aa51. Read the comment docs.

Fixes issue sqlfluff#3651.

Previously, the first argument to the `convert` redshift function was
interpreted as a column reference rather than a data type. This could
cause rule L027 to fail since the data type wasn't qualified with a
table name even though that doesn't make sense. This adds explicit
handling for `convert` to eliminate that issue.
Copy link
Member

@tunetheweb tunetheweb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Btw ideally don’t force push if you can. Was fine for this one, but if a PR review takes a few iterations the force pushing can make it difficult to see what’s changed in each one.

@tunetheweb tunetheweb merged commit db168f5 into sqlfluff:main Jul 23, 2022
@tunetheweb tunetheweb changed the title Add handling for redshift convert function data type argument Add handling for Redshift CONVERT function data type argument Jul 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants