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
[MYSQL] convert explicitely smallint and tinyint #35897
Conversation
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 good I think. Added some comments and a suggestion to get the CI to not run mysql_tests during the integration tests when database is sqlite.
To avoid this kind of issue, maybe it makes more sense to think about enhance convert value to float64 to support also string type?
Maybe. Is the type really string, isn't it string array? If you would like to evaluate that, please push changes to this PR or open an alternative PR so that we can understand what it actually means in terms of code and changes.
i think this fix is urgent, let's fix the issue and i would create a ticket for the improvement, we can discuss that next week. |
Are these specifically for NULLABLE smallint / tinyint? will this also work for non-nullable columns with these types? |
they are working for both nullable and no nullable. |
* [MYSQL] convert explicitely smallint and tinyint * clean up code * fix comments (cherry picked from commit 73fdd9d)
* [MYSQL] convert explicitely smallint and tinyint * clean up code * fix comments
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #35876
Special notes for your reviewer:
seems when smallint or tinyint is nullable or not would impact its scantype. when they are nullable, scantype becomes nullableint64, for which we would generate the default string converter.