[MDEV-4872] Inserting a huge number into a TIME column produces a wrong result Created: 2013-08-09  Updated: 2022-09-08

Status: Open
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.3, 5.5.32, 5.3.12
Fix Version/s: 5.5

Type: Bug Priority: Minor
Reporter: Alexander Barkov Assignee: Alexander Barkov
Resolution: Unresolved Votes: 0
Labels: None


 Description   

MariaDB [test]> DROP TABLE IF EXISTS t1; CREATE TABLE t1 (a TIME); INSERT INTO t1 VALUES (100000000000000000); SHOW WARNINGS; SELECT * FROM t1;
Query OK, 0 rows affected (0.00 sec)
 
Query OK, 0 rows affected (0.07 sec)
 
Query OK, 1 row affected, 1 warning (0.00 sec)
 
+---------+------+----------------------------------------+
| Level   | Code | Message                                |
+---------+------+----------------------------------------+
| Warning | 1265 | Data truncated for column 'a' at row 1 |
+---------+------+----------------------------------------+
1 row in set (0.00 sec)
 
+----------+
| a        |
+----------+
| 00:00:00 |
+----------+
1 row in set (0.00 sec)

The expected result is 'maximum possible value', which is '838:59:59'.

MySQL 5.5 and 5.6 correctly insert the maximum possible value.


Generated at Thu Feb 08 06:59:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.