Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5(EOL), 10.0(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL)
Description
This problem is similar to MDEV-11497, but now for the simple CASE operator:
CASE suffers from the same problem:
DROP TABLE IF EXISTS t1; |
CREATE TABLE t1 (a BIGINT, b BIGINT UNSIGNED); |
INSERT INTO t1 VALUES (-9223372036854775808,18446744073709551615); |
SELECT
|
CASE -1 |
WHEN -9223372036854775808 THEN 'one' |
WHEN 18446744073709551615 THEN 'two' |
END; |
+-------------------------------------------------------------------------------------------------+
|
| CASE -1
|
WHEN -9223372036854775808 THEN 'one'
|
WHEN 18446744073709551615 THEN 'two'
|
END |
|
+-------------------------------------------------------------------------------------------------+
|
| two |
|
+-------------------------------------------------------------------------------------------------+
|
The expected result is to return NULL.
Attachments
Issue Links
- blocks
-
MDEV-4912 Data type plugin API version 1
- Closed
- relates to
-
MDEV-11555 CASE with a mixture of TIME and DATETIME returns a wrong result
- Closed
-
MDEV-11497 Wrong result for (int_expr IN (mixture of signed and unsigned expressions))
- Closed