Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Minor
-
Resolution: Unresolved
-
5.1.67, 5.2.14, 5.3.12, 5.5.36, 10.0.10
-
None
Description
The BIT field works well as a number in most cases,
but not when casting it to temporal data types:
DROP TABLE IF EXISTS t1;
|
CREATE TABLE t1 (a BIT(8));
|
INSERT INTO t1 VALUES (0xFF);
|
SELECT a+0,CAST(255 AS TIME), CAST(a AS TIME) FROM t1;
|
SHOW WARNINGS;
|
returns
+------+-------------------+-----------------+
|
| a+0 | CAST(255 AS TIME) | CAST(a AS TIME) |
|
+------+-------------------+-----------------+
|
| 255 | 00:02:55 | 00:00:00 |
|
+------+-------------------+-----------------+
|
1 row in set, 1 warning (0.00 sec)
|
 |
+---------+------+----------------------------------------+
|
| Level | Code | Message |
|
+---------+------+----------------------------------------+
|
| Warning | 1292 | Truncated incorrect time value: '\xFF' |
|
+---------+------+----------------------------------------+
|
The expected result for CAST(a AS TIME) is '00:02:55'
without warnings.