Update the mysql lexer keywords#2970
Merged
birkenfeld merged 1 commit intopygments:masterfrom Feb 20, 2026
Merged
Conversation
8c1b3fb to
8487a48
Compare
Member
|
LGTM, thanks! |
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
3 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.
This PR introduces the following changes:
The
CHAR BYTEalias is now supported.Previously,
BYTEhad not been understood to be part of a type alias and was registered only as a reserved keyword.Many additional keywords and reserved keywords have been found by changing the mysql GitHub branch from
8.0totrunk.A number of existing keywords have been removed in the mysql keyword list since mysql 8.0, but for backwards compatibility these removals were discarded in the pygments keywords list.
The result is a number of additions to the list of mysql keywords that pygments recognizes, with zero removals. Note that
byteappears to be a removal, but is actually moved up to the tuple ofMYSQL_DATATYPES, as noted in the first bullet point above.