Inconsistent value saturation behavior for DATE and DATETIME between INSERT and UPDATE, cpimport

Build tested:

mscadmin> getsoft
getsoftwareinfo Wed Sep 14 12:59:32 2016

Name : mariadb-columnstore-platform
Version : 1.0.3
Release : 1
Architecture: x86_64
Install Date: Mon 12 Sep 2016 09:48:35 AM CDT

There are couple tickets in this release make changes related to DATE and DATETIME

MCOL-171 Added support for 0000-00-00, and it also changed value saturation behavior for DATE and DATETIME datatypes.

MCOL-274 Change support value range

Columnstore 1.0.2 value saturation behavior
Both DML statements and cpimport saturate out-of-range values to NULL

Columnstore 1.0.3 value saturation behavior

Note: The mininum supported year value for DATE and DATETIME has been changed from 1400 to 1000, matching standard MySQL

INSERT saturates to 0000-00-00
LDI saturates to 0000-00-00
UPDATE saturates to NULL
cpimport saturates to NULL

Standard MySQL DML statements saturates to NULL so I suggest we fix both UPDATE and cpimport to do the same.

Changes also needed in the Syntax Guide.

Page 8

Need to update the supported value range for DATE and DATETIME datatypes.

Page 10

For the date and datetime datatypes, a value outside of the supported range (1400-01-01 to 9999-12-31) will be stored as NULL in InfiniDB

needs to be updated to

For the date and datetime datatypes, a value outside of the supported range (1000-01-01 to 9999-12-31) will be stored as 0000-00-00 in ColumnStore