Bug #116846 | The logical error of the NULLIF function in the WHERE condition. | ||
---|---|---|---|
Submitted: | 2 Dec 2024 14:42 | Modified: | 4 Dec 2024 11:09 |
Reporter: | wang jack | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Data Types | Severity: | S3 (Non-critical) |
Version: | 8.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[2 Dec 2024 14:42]
wang jack
[2 Dec 2024 15:42]
MySQL Verification Team
Hi Mr. jack, Thank you for your bug report. However, it is not a bug. There are several reasons why this is not a bug, but we shall cite only two. First of all, USER() function always return the error. Second, you are mixing values of the different types in a single expression, which is not allowed by SQL Standard. You are mixing CHAR/VARCHAR with BOOLEAN. in your case, those two values have a common denominator as DOUBLE, which can not work as a BOOLEAN value. Not a bug.
[4 Dec 2024 11:09]
MySQL Verification Team
Hi Mr. jack, It turns out that your test case involves data types that we are covering by our conversions. Verified as reported.