Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.0.3, 5.5.31, 5.3.12
Description
A confusing warning is printed in the following SQL script:
mysql> select CAST(TIME('10:20:30') AS DATE) + INTERVAL 1 DAY; show warnings; |
+-------------------------------------------------+ |
| CAST(TIME('10:20:30') AS DATE) + INTERVAL 1 DAY | |
+-------------------------------------------------+ |
| NULL | |
+-------------------------------------------------+ |
1 row in set, 1 warning (0.00 sec) |
 |
+---------+------+----------------------------------------------+ |
| Level | Code | Message | |
+---------+------+----------------------------------------------+ |
| Warning | 1292 | Truncated incorrect date value: '0000-00-00' | |
+---------+------+----------------------------------------------+ |
1 row in set (0.00 sec) |
The word "Truncated" is not appropriate here.
The expected warning is something like:
"Incorrect datetime value: '0000-00:00 00:00:00'"
or
"Incorrect date value: '0000-00:00".
A warning generated in MySQL-5.1 and 5.5 is also not perfect:
Incorrect datetime value: '10:20:30'
But at least does not contain the confusing word "Truncated".
Attachments
Issue Links
- is blocked by
-
MDEV-8778 Temporal fields with zero dates do not respect sql_mode=traditional
- Open
-
MDEV-11137 TIMESTAMP has 2-level logic for default values
- Open