[MCOL-170] Invalid dates are truncacted to NULL instead of 0000-00-00 Created: 2016-06-22  Updated: 2016-09-19  Resolved: 2016-09-19

Status: Closed
Project: MariaDB ColumnStore
Component/s: ExeMgr
Affects Version/s: None
Fix Version/s: 1.0.3

Type: Bug Priority: Major
Reporter: Justin Swanhart (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by MCOL-171 0000-00-00 dates are not supported an... Closed

 Description   

MariaDB [(none)]> use test;
Database changed
MariaDB [test]> create table t1(d1 date) engine=myisam;
Query OK, 0 rows affected (0.01 sec)

MariaDB [test]> insert into t1 values (.1);
Query OK, 1 row affected, 1 warning (0.00 sec)

MariaDB [test]> select * from t1;
------------

d1

------------

0000-00-00

------------
1 row in set (0.00 sec)

MariaDB [test]> drop table t1;
Query OK, 0 rows affected (0.00 sec)

MariaDB [test]> create table t1(d1 date) engine=columnstore;
Query OK, 0 rows affected (0.26 sec)

MariaDB [test]> insert into t1 values (.1);
Query OK, 1 row affected, 1 warning (0.22 sec)

MariaDB [test]> select * from t1;
------

d1

------

NULL

------
1 row in set (0.06 sec)

 Comments   
Comment by Justin Swanhart (Inactive) [ 2016-06-22 ]

affects date and datetime columns

Comment by David Thompson (Inactive) [ 2016-09-19 ]

Fix for MCOL-171 addresses this.

Generated at Thu Feb 08 02:19:02 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.