[MCOL-171] 0000-00-00 dates are not supported and are munged to NULL with no warnings Created: 2016-06-22 Updated: 2016-10-11 Resolved: 2016-09-13 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | DMLProc |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Justin Swanhart (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | relnote | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Sprint: | 1.0.3 | ||||||||||||||||||||||||||||
| Description |
|
create table t2(d date, dt datetime) engine=columnstore; MariaDB [test]> insert into t2 values ('0000-00-00','0000-00-00'); MariaDB [test]> select * from t2;
-----
----- MariaDB [test]> select * from t2 where dt='0000-00-00'; MariaDB [test]> select * from t2 where dt is null;
-----
----- |
| Comments |
| Comment by Andrew Hutchings (Inactive) [ 2016-08-19 ] |
|
Marked as In Progress as this is getting fixed as part of my fix for |
| Comment by Andrew Hutchings (Inactive) [ 2016-08-23 ] |
|
note that year < 1400 is also invalid in ColumnStore's checks. Will be fixed as part of my patch |
| Comment by Andrew Hutchings (Inactive) [ 2016-08-24 ] |
|
The fix for this is now in my patch for Note: after merge this page will need updating as the DATETIME limits are now in-line with MariaDB's with my fix: https://mariadb.com/kb/en/mariadb/columnstore-data-types/ |
| Comment by Andrew Hutchings (Inactive) [ 2016-08-30 ] |
|
On hold for now. My fix for this is working great, but without fixing |
| Comment by Andrew Hutchings (Inactive) [ 2016-08-30 ] |
|
https://github.com/mariadb-corporation/mariadb-columnstore-engine/pull/5 This is a fix for |
| Comment by David Hall (Inactive) [ 2016-09-02 ] |
|
Test and close |
| Comment by Daniel Lee (Inactive) [ 2016-09-13 ] |
|
Build verified: Name : mariadb-columnstore-platform |