Bug #81950 | when cast failed mysql return different results | ||
---|---|---|---|
Submitted: | 21 Jun 2016 11:06 | Modified: | 27 Jul 2016 9:41 |
Reporter: | 帅 Bang | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: DML | Severity: | S3 (Non-critical) |
Version: | 5.6 | OS: | Linux |
Assigned to: | CPU Architecture: | Any |
[21 Jun 2016 11:06]
帅 Bang
[5 Jul 2016 2:14]
帅 Bang
Excuse me, is there any progress on this issue? thx
[27 Jul 2016 9:41]
MySQL Verification Team
Hello Bang, Thank you for the bug report and test case. Imho this is not a bug, as per manual 'Inserting a value into a date or time column that is illegal for the data type. The column is set to the appropriate zero value for the type' See https://dev.mysql.com/doc/refman/5.6/en/insert.html. In case of CAST - If you try to convert an invalid expression to a date, CAST() returns NULL and which is expected behavior. Thanks, Umesh