expression: fix incompatible last_day func behavior in sql mode (#25953)

[ti-srebot]

cherry-pick #25953 to release-5.0
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/26000

After apply modifications, you can push your change to this PR via:

git push [email protected]:ti-srebot/tidb.git pr/26000:release-5.0-5a07699871d7

---

Signed-off-by: lzmhhh123 [email protected]

What problem does this PR solve?

Problem Summary:

in tidb:

tidb(localhost:4000) > select last_day(str_to_date('202106', '%Y%m'));
+-----------------------------------------+
| last_day(str_to_date('202106', '%Y%m')) |
+-----------------------------------------+
| NULL                                    |
+-----------------------------------------+
1 row in set, 1 warning (0.00 sec)

tidb(localhost:4000) > set @@sql_mode = "";
Query OK, 0 rows affected (0.00 sec)

tidb(localhost:4000) > select last_day(str_to_date('202106', '%Y%m'));
+-----------------------------------------+
| last_day(str_to_date('202106', '%Y%m')) |                                                                                                                                             
+-----------------------------------------+
| NULL                                    |
+-----------------------------------------+
1 row in set, 1 warning (0.00 sec)

tidb(localhost:4000) > show warnings;
+---------+------+----------------------------------------+
| Level   | Code | Message                                |
+---------+------+----------------------------------------+
| Warning | 1292 | Incorrect datetime value: '2021-06-00' |
+---------+------+----------------------------------------+
1 row in set (0.00 sec)

in mysql 8.0.22

mysql > select last_day(str_to_date('202106', '%Y%m'));
+-----------------------------------------+
| last_day(str_to_date('202106', '%Y%m')) |
+-----------------------------------------+
| NULL                                    |
+-----------------------------------------+
1 row in set, 1 warning (0.00 sec)

mysql > set @@sql_mode="";
Query OK, 0 rows affected (0.01 sec)

mysql > select last_day(str_to_date('202106', '%Y%m'));
+-----------------------------------------+
| last_day(str_to_date('202106', '%Y%m')) |
+-----------------------------------------+
| 2021-06-30                              |
+-----------------------------------------+
1 row in set (0.00 sec)

What is changed and how it works?

How it Works:

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Unit test
• Integration test

Release note

• fix incompatible last_day func behavior in sql mode

[ti-srebot]

/run-all-tests

[ti-srebot]

@lzmhhh123 you're already a collaborator in bot's repo.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• ichn-hu
• tangenta

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.

[lzmhhh123]

/cc @ichn-hu

[XuHuaiyu]

/merge

[ti-chi-bot]

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

Commit hash: 699c63d

[ti-chi-bot]

@ti-srebot: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.