Details
-
Bug
-
Status: Closed (View Workflow)
-
Trivial
-
Resolution: Fixed
-
10.0.0, 5.5.28a, 5.3.11
-
None
-
None
Description
It's rather a cosmetic difference, but I want to fix our failures on MySQL engines suite (again), and this is one of them. So, if it's intended behavior, please reassign the bug back to me so I update the result file for engines/funcs/r/date_function.
MariaDB 5.3, 5.5, 10.0:
CREATE TABLE t1(c1 TIMESTAMP NOT NULL) ENGINE=MyISAM; |
INSERT INTO t1 VALUES('2008-02-29'); |
SELECT FROM_DAYS(c1) FROM t1; |
# FROM_DAYS(c1)
|
# NULL |
MySQL 5.1, 5.5, 5.6, MariaDB 5.2:
CREATE TABLE t1(c1 TIMESTAMP NOT NULL) ENGINE=MyISAM; |
INSERT INTO t1 VALUES('2008-02-29'); |
SELECT FROM_DAYS(c1) FROM t1; |
# FROM_DAYS(c1)
|
# 0000-00-00
|
No warnings on either version.
Attachments
Issue Links
- relates to
-
MDEV-3990 engines/* and storage_engine tests and result files went out of sync with current MariaDB code
- Closed