[MDEV-5843] Wrong warning when inserting zero date into TIMESTAMP with SQL_MODE=no_zero_date Created: 2014-03-13  Updated: 2022-09-08

Status: Open
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.5.36, 10.0.9
Fix Version/s: 5.5

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


 Description   

mysql> DROP TABLE IF EXISTS t1; CREATE TABLE t1 (a DATE, b DATETIME, c TIMESTAMP); SET SQL_MODE='no_zero_date'; INSERT INTO t1 VALUES (0,0,0); SHOW WARNINGS;
Query OK, 0 rows affected (0.05 sec)
 
Query OK, 0 rows affected (0.21 sec)
 
Query OK, 0 rows affected (0.00 sec)
 
Query OK, 1 row affected, 3 warnings (0.00 sec)
 
+---------+------+--------------------------------------------+
| Level   | Code | Message                                    |
+---------+------+--------------------------------------------+
| Warning | 1264 | Out of range value for column 'a' at row 1 |
| Warning | 1264 | Out of range value for column 'b' at row 1 |
| Warning | 1265 | Data truncated for column 'c' at row 1     |
+---------+------+--------------------------------------------+
3 rows in set (0.00 sec)

The warning for the TIMESTAMP column is wrong. Nothing was truncated.
The correct warnings is 'Out of range...'


Generated at Thu Feb 08 07:07:28 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.