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
sql: fix some spelling errors #20727
Conversation
Please make sure that the changes to |
Review status: 0 of 7 files reviewed at latest revision, all discussions resolved, some commit checks pending. Comments from Reviewable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
"FLOAT4": ColumnType_REAL, | ||
"REAL": ColumnType_REAL, | ||
"FLOAT8": ColumnType_DOUBLE_PRECISION, | ||
"DOUBLE PRECISION": ColumnType_DOUBLE_PRECISION, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fairly sure this is fixing a real but minor bug - I think without this change users wouldn't be able to specify a DOUBLE PRECISION type with a precision type omdifier. Or something like that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there's a test failure so you might be right. I'll update the release notes if this is the case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, was a minor bug, added the release note.
Comments from Reviewable |
Release note: (sql) A small spelling bug made it such that a `DOUBLE PRECISION` specified type would erroneously display as a float. Interally these are the same type, so this was just an bug on showing the correct type alias when calling `SHOW COLUMNS`.
044f156
to
8d13170
Compare
Release note: None