Bug #94614 | In cases like ifnull(datetime(2), time(3)), the wrong answer is returned. | ||
---|---|---|---|
Submitted: | 10 Mar 2019 2:47 | Modified: | 25 Apr 2019 2:07 |
Reporter: | Hope Lee (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S2 (Serious) |
Version: | 8.0.15-rds-dev, 8.0.15, 5.7.25,5.6.43 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[10 Mar 2019 2:47]
Hope Lee
[10 Mar 2019 5:27]
MySQL Verification Team
Hello Lee, Thank you for the report and test case. regards, Umesh
[25 Apr 2019 2:07]
Jon Stephens
Documented fix in the MySQL 8.0.18 changelog as follows: The resolution procedure for the IFNULL() function differed from that for all other functions derived from CASE(), including COALESCE(), which caused incorrect length information to be generated for certain numeric expressions. Closed.