Fix rule failures for MySQL/MariaDB with backticked identifiers#6702
Merged
keraion merged 2 commits intosqlfluff:mainfrom Mar 29, 2025
Merged
Fix rule failures for MySQL/MariaDB with backticked identifiers#6702keraion merged 2 commits intosqlfluff:mainfrom
keraion merged 2 commits intosqlfluff:mainfrom
Conversation
Contributor
Coverage Results ✅ |
keraion
reviewed
Mar 28, 2025
keraion
reviewed
Mar 28, 2025
pprkut
force-pushed
the
mariadb_backtick
branch
from
1891900 to
1d9a691
Compare
pprkut
force-pushed
the
mariadb_backtick
branch
from
1d9a691 to
3969059
Compare
This was referenced Apr 1, 2025
3 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 #5356
Are there any other side effects of this change that we should be aware of?
Not that I can see.
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.