feat: load data (Incorrect timestamp value) into a StoneDB table, but No warnning was returned

[davidshiz]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Please confirm if bug report does NOT exists already ?

• I confirm there is no existing issue for this

Describe the problem

The TIMESTAMP data type is used for values that contain both date and time parts. TIMESTAMP has a
range of '1970-01-01 00:00:01' UTC to '2038-01-19 03:14:07' UTC;

when I am trying to load data into a StoneDB table and all of my timestamps (out of range) are being loaded as '0000-00-00 00:00:00', and no warning.

Expected behavior

A warning message should be returned

How To Reproduce

ubuntu@ubuntu:~$ cat /home/ubuntu/test
1,2056-08-22 11:24:49

CREATE TABLE `test` (
  `id` int(11) DEFAULT NULL,
  `t` timestamp NULL DEFAULT NULL
) ENGINE=TIANMU DEFAULT CHARSET=utf8mb4;

load data local infile '/home/ubuntu/test' into table test fields terminated by ',';

Environment

ubuntu@ubuntu:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.4 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.4 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

ubuntu@ubuntu:~$ /stonedb57/install/bin/mysqld --version
/stonedb57/install/bin/mysqld Ver 5.7.36_v1.0.1_beta_2-StoneDB for Linux on x86_64 (build-)
build information as follow:
Repository address: https://github.com/stoneatom/stonedb.git:stonedb-5.7-dev
Branch name: stonedb-5.7-dev
Last commit ID: 208f79d
Last commit time: Date: Sat Sep 17 16:19:42 2022 +0800
Build time: Date: Fri Sep 23 14:14:27 CST 2022

Are you interested in submitting a PR to solve the problem?

• Yes, I will!

[hustjieke]

MySQL result, The same with Tianmu, but Tianmu has no warnings:

mysql> show warnings;
+---------+------+--------------------------------------------+
| Level   | Code | Message                                    |
+---------+------+--------------------------------------------+
| Warning | 1264 | Out of range value for column 't' at row 1 |
+---------+------+--------------------------------------------+
1 row in set (0.00 sec)

mysql> select * from t;
+------+---------------------+
| id   | t                   |
+------+---------------------+
|    1 | 0000-00-00 00:00:00 |
+------+---------------------+
1 row in set (0.00 sec)

[adofsauron]

Using insert statements to go through the insert process, timestamp is recognized when it crosses the boundary

mysql> INSERT test_timestamp(a) VALUES('2038-01-19 03:14:07');
ERROR 1292 (22007): Incorrect datetime value: '2038-01-19 03:14:07' for column 'a' at row 1
mysql> INSERT test_timestamp(a) VALUES('2038-01-19 03:14:06');
ERROR 1292 (22007): Incorrect datetime value: '2038-01-19 03:14:06' for column 'a' at row 1
mysql> INSERT test_timestamp(a) VALUES('2038-01-18 03:14:06');
Query OK, 1 row affected (0.00 sec)