types: fix parse date inconsistent with MySQL

[lonng]

Signed-off-by: Lonng heng@lonng.org

What problem does this PR solve?

The parse string to date inconsistent with MySQL:

mysql> select convert('1201012736.0000', date);
+----------------------------------+
| convert('1201012736.0000', date) |
+----------------------------------+
| NULL                             |
+----------------------------------+
1 row in set, 1 warning (0.01 sec)

mysql> select convert('1201012136.0000', date);
+----------------------------------+
| convert('1201012136.0000', date) |
+----------------------------------+
| 2012-01-01                       |
+----------------------------------+
1 row in set, 1 warning (0.00 sec)

The MySQL will check the hms even if the target type is Date.
Mirror PR: tikv/tikv#6442

What is changed and how it works?

Check Date via checkDatetimeType

Check List

Tests

• Unit test

[qw4990]

LGTM

[lonng]

/run-all-tests

[wjhuang2016]

LGTM

[sre-bot]

cherry pick to release-3.0 failed

[sre-bot]

It seems that, not for sure, we failed to cherry-pick this commit to release-3.0. Please comment '/run-cherry-picker' to try to trigger the cherry-picker if we did fail to cherry-pick this commit before. @lonng PTAL.

[reafans]

/run-cherry-picker

[sre-bot]

cherry pick to release-3.0 in PR #16242