MySQL: Allow optional SIGNED suffix on integer data types#1985
Merged
iffyio merged 1 commit intoapache:mainfrom Aug 1, 2025
Merged
MySQL: Allow optional SIGNED suffix on integer data types#1985iffyio merged 1 commit intoapache:mainfrom
SIGNED suffix on integer data types#1985iffyio merged 1 commit intoapache:mainfrom
Conversation
iffyio
reviewed
Jul 31, 2025
In MySQL, a data type like `INT(20) SIGNED` is equivalent to `INT(20)`. In other dialects, this may be interpreted differently; e.g. in Postgres, `SELECT 1::integer signed` indicates an alias of "signed". So we parse the optional `SIGNED` suffix only on dialects that allow it (I currently don't know of any other than MySQL).
mvzink
force-pushed
the
push-tqonuxmzypyv
branch
from
deed2ce to
28d2183
Compare
ayman-sigma
pushed a commit
to sigmacomputing/sqlparser-rs
that referenced
this pull request
Feb 3, 2026
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.
In MySQL, a data type like
INT(20) SIGNEDis equivalent toINT(20). In other dialects, this may be interpreted differently; e.g. in Postgres,SELECT 1::integer signedindicates an alias of "signed". So we parse the optionalSIGNEDsuffix only on dialects that allow it (I currently don't know of any other than MySQL).