Bug #68557 | sjis changes in 5.5 break date parsing | ||
---|---|---|---|
Submitted: | 4 Mar 2013 8:12 | Modified: | 12 Nov 2019 5:21 |
Reporter: | Hartmut Holzgraefe | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Server: Charsets | Severity: | S3 (Non-critical) |
Version: | mysql 5.5.30 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[4 Mar 2013 8:12]
Hartmut Holzgraefe
[4 Mar 2013 9:53]
MySQL Verification Team
Hello Hartmut, Thank you for the report. Verified as described. Thanks, Umesh
[12 Nov 2019 5:21]
Chandan Kunal
Posted by developer: The main source of the problem is allowing sloppy syntax in the first place. If we had stuck to strict SQL (and ISO8601) compliance, this bug would never have occurred. This is also why we consider deprecating sloppy syntax in e.g date/time literals. Fixing this bug will take us in the wrong direction also sjis and ujis are broken in various ways.. CAST function can be used as workaround for this bug. For example query mentioned in the bug page can be reworked as follows: SELECT * FROM t1 WHERE d = CAST('2013/02/28' AS datetime);