s4uliu5,
Thanks for the report.
This is an upstream (MySQL) bug, reproducible on MySQL 5.5+. In such cases, we also report the bug in bugs.mysql.com, to inform upstream about the issue. Are you willing to do it, or should we do it on your behalf?
bar,
Even though it's an upstream bug, could you please take a quick look, if it's related to the temporal types area that you've been working on, maybe it will be easier to fix it than to wait for the upstream fix.
Here is even smaller test case (although the original one is also quite compact):
SET NAMES utf8;
|
|
DROP TABLE IF EXISTS t1;
|
CREATE TABLE t1 (d DATE) ENGINE=MyISAM;
|
|
INSERT INTO t1 VALUES ('1999-11-11'),('2014-02-04');
|
|
SELECT DISTINCT
|
d,
|
cast(d as char),
|
nullif(d,"2000-01-01") bad,
|
nullif(cast(d as char),"2000-01-01") good
|
FROM t1;
|
|
DROP TABLE t1;
|
Result:
+------------+-----------------+------+------------+
|
| d | cast(d as char) | bad | good |
|
+------------+-----------------+------+------------+
|
| 1999-11-11 | 1999-11-11 | 199 | 1999-11-11 |
|
| 2014-02-04 | 2014-02-04 | 201 | 2014-02-04 |
|
+------------+-----------------+------+------------+
|
s4uliu5,
Thanks for the report.
This is an upstream (MySQL) bug, reproducible on MySQL 5.5+. In such cases, we also report the bug in bugs.mysql.com, to inform upstream about the issue. Are you willing to do it, or should we do it on your behalf?
bar,
Even though it's an upstream bug, could you please take a quick look, if it's related to the temporal types area that you've been working on, maybe it will be easier to fix it than to wait for the upstream fix.
Here is even smaller test case (although the original one is also quite compact):
d,
Result:
+------------+-----------------+------+------------+
| d | cast(d as char) | bad | good |
+------------+-----------------+------+------------+
| 1999-11-11 | 1999-11-11 | 199 | 1999-11-11 |
| 2014-02-04 | 2014-02-04 | 201 | 2014-02-04 |
+------------+-----------------+------+------------+