| Bug #95741 | Metadata query uses UPPER() around numeric expression | ||
|---|---|---|---|
| Submitted: | 11 Jun 2019 21:42 | Modified: | 13 Sep 2019 22:13 |
| Reporter: | jess Balint | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / J | Severity: | S3 (Non-critical) |
| Version: | 8.0.16 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[12 Jun 2019 6:26]
MySQL Verification Team
Hello jess Balint, Thank you for the report and feedback. regards, Umesh
[25 Jun 2019 8:22]
Alexander Soklakov
Thanks Jess!
[6 Jul 2019 11:12]
Filipe Silva
Thank you Jess. Nice to see you around!
[13 Sep 2019 22:13]
Daniel So
Posted by developer: Added the following entry into the MySQL Connecotr/J 8.0.18 changelog: "A minor code improvement has been put into DatabaseMetaDataUsingInfoSchema.getColumns()."

Description: DatabaseMetaDataUsingInfoSchema contains the following code: sqlBuf.append("UPPER(CASE"); sqlBuf.append(" WHEN IS_NULLABLE='NO' THEN "); sqlBuf.append(columnNoNulls); sqlBuf.append(" ELSE CASE WHEN IS_NULLABLE='YES' THEN "); sqlBuf.append(columnNullable); sqlBuf.append(" ELSE "); sqlBuf.append(columnNullableUnknown); sqlBuf.append(" END END) AS NULLABLE,"); The UPPER() around this expression is unnecessary How to repeat: see above