types: fix creating partition tables fail in ANSI_QUOTES mode

[djshow832]

What problem does this PR solve?

Issue Number: close #35281, #24980

Problem Summary:

• the expression '2022-01-01 00:00:00' is formatted as "2022-01-01 00:00:00" in buildRangePartitionDefinitions
• ParseSimpleExprWithTableInfo creates the statement select "2022-01-01 00:00:00" to eval the value
• "2022-01-01 00:00:00" is taken as an identifier since sql_mode = 'ANSI_QUOTES'.

What is changed and how it works?

Format the string with single quotes, because single quotes always work.
In MySQL, even if sql_mode doesn't contain ANSI_QUOTES, the expression still is single-quoted:

mysql> show create table t;
+-------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Table | Create Table                                                                                                                                                                                                                                                                                                                                              |
+-------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| t     | CREATE TABLE `t` (
  `a` int DEFAULT NULL,
  `b` varchar(255) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci
/*!50500 PARTITION BY LIST  COLUMNS(a,b)
(PARTITION pLow VALUES IN ((1,'1'),(2,'2'),(3,'3'),(5,'5'),(8,'8')) ENGINE = InnoDB,
 PARTITION pMax VALUES IN ((10,'10'),(11,'11'),(12,'12')) ENGINE = InnoDB) */ |
+-------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

mysql> select @@sql_mode;
+-----------------------------------------------------------------------------------------------------------------------+
| @@sql_mode                                                                                                            |
+-----------------------------------------------------------------------------------------------------------------------+
| ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION |
+-----------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• mjonss
• tiancaiamao

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[mjonss]

LGTM, just one suggestion for extended test.

[sre-bot]

Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/3e10ae0618d9cdaabda613132999b41d95033fdf

[djshow832]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 5e0e424

[djshow832]

/run-all-tests

[hawkingrei]

/run-mysql-test

[mjonss]

/run-mysql-test

[hawkingrei]

/run-mysql-test

[hawkingrei]

/run-mysql-test tidb-test=pr/1812

[sre-bot]

TiDB MergeCI notify

🔴 Bad News! New failing [2] after this pr merged.
These new failed integration tests seem to be caused by the current PR, please try to fix these new failed integration tests, thanks!

CI Name	Result	Duration	Compare with Parent commit
idc-jenkins-ci-tidb/integration-common-test	🟥 failed 2, success 9, total 11	14 min	New failing
idc-jenkins-ci-tidb/common-test	🟥 failed 2, success 10, total 12	10 min	New failing
idc-jenkins-ci/integration-cdc-test	🟢 all 34 tests passed	24 min	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-2	🟢 all 28 tests passed	5 min 36 sec	Existing passed
idc-jenkins-ci-tidb/integration-ddl-test	🟢 all 6 tests passed	4 min 58 sec	Existing passed
idc-jenkins-ci-tidb/tics-test	🟢 all 1 tests passed	4 min 57 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-1	🟢 all 26 tests passed	4 min 51 sec	Existing passed
idc-jenkins-ci-tidb/mybatis-test	🟢 all 1 tests passed	3 min 22 sec	Existing passed
idc-jenkins-ci-tidb/integration-compatibility-test	🟢 all 1 tests passed	3 min 2 sec	Existing passed
idc-jenkins-ci-tidb/plugin-test	🟢 build success, plugin test success	4min	Existing passed