ranger: fix the range construction behavior when the column's type is YEAR (#23559)

[ti-srebot]

cherry-pick #23559 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/24018

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

git push git@github.com:ti-srebot/tidb.git pr/24018:release-5.0-670b5fbcf5ad

---

Signed-off-by: wjhuang2016 huangwenjun1997@gmail.com

What problem does this PR solve?

Issue Number: close #23508

Problem Summary:

The type of year should be int, not double.

What is changed and how it works?

Use ConvertToMysqlYear() to adjust the year constant, and handle some corner cases.

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Unit test

• Manual test (add detailed scripts or steps below)

Start a tidb cluster.
CREATE TABLE PK_S_MULTI_42_2 ( COL1 year(4) NOT NULL, COL2 year(4) NOT NULL, COL3 year(4) DEFAULT NULL, PRIMARY KEY (COL1,COL2) clustered);
mysql> select * from PK_S_MULTI_42_2 where col2 between 2154 and 2154 AND col3 > 2153;
Empty set (0.00 sec)

Side effects

Release note

• fix wrong year type

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[ti-srebot]

/run-all-tests

[ti-srebot]

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

[eurekaka]

@wjhuang2016 please take a look at the failed CI.

[qw4990]

Please resolve conflicts @wjhuang2016

[lysu]

Please resolve conflicts @wjhuang2016 🤣 ... too many test cases false-fail everyday in 5.0

[eurekaka]

Not critical enough to be merged into 5.0.