TSQL: Add labels, as well as GRANT/DENY/REVOKE
#3149
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## main #3149 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 165 165
Lines 12266 12278 +12
=========================================
+ Hits 12266 12278 +12
Continue to review full report at Codecov.
|
tunetheweb
changed the title
GRANT/DENY/REVOKE`GRANT/DENY/REVOKE
tunetheweb
changed the title
GRANT/DENY/REVOKEGRANT/DENY/REVOKE
barrywhart
approved these changes
Apr 22, 2022
| @@ -1 +1,3 @@ | |||
| GOTO Branch_Three; | |||
| Branch_Three: | |||
| RETURN | |||
There was a problem hiding this comment.
Is this related to the rest of the PR?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brief summary of the change made
Fixes #1780
Fixes #3147
Also should prevent horrible Keyword Missing stack traces errors for T-SQL as the
AccessStatementSegmenthad quite a lot of keywords that didn't exist in T-SQL.Are there any other side effects of this change that we should be aware of?
The AccessStatementSegment is undoubtedly not complete as there's a LOT of options in there. But this is the basic and allows it to be added to.
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:
.ymlrule test cases intest/fixtures/rules/std_rule_cases..sql/.ymlparser 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.