Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
11.8.3
-
Not for Release Notes
Description
Run the following two cases.
-- case 1
|
CREATE TABLE t1 (c1 INT); |
INSERT INTO t1 VALUES (12080247); |
SELECT (c1 = (CAST(0 AS TIME))) FROM t1; -- {1}, expected: {0} |
-- case 2
|
CREATE TABLE t1 (c1 BIGINT); |
INSERT INTO t1 VALUES (12080247); |
SELECT (c1 = (CAST(0 AS TIME))) FROM t1; -- {0} |
I think that case 2 is correct.
Attachments
Issue Links
- duplicates
-
MDEV-38006 Inconsistent behaviors when casting into time
-
- Closed
-
- relates to
-
MDEV-4837 Comparing a TIME value with an illegal time representation returns TRUE
-
- Confirmed
-