expression: fix wrong caseWhen function for enum type (#29454)

[ti-srebot]

cherry-pick #29454 to release-4.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/29508

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

git push git@github.com:ti-srebot/tidb.git pr/29508:release-4.0-ae65cae8d04c

---

What problem does this PR solve?

Issue Number: close #29357

Problem Summary:

What is changed and how it works?

There are two problem in this issue:
Problem 1:

1. caseWhenFunctionClass.getFunction get fieldType Enum from children, and construct scalarFunction caseWhenString.
2. compareFunctionClass.getFunction get fieldType Int and Enum, and set EnumSetAsInt flag, but not re-construct caseWhen function.
3. Get the final scalarFunction EQInt(1, CaseWhenString(0, Enum)) and pushdown. CaseWhenString can't get int value.

Problem 2:

[tidb]> SELECT 5 = (case when 0 <=> 1 then a else a end) from t;
ERROR 1105 (HY000): baseBuiltinFunc.vecEvalInt() should never be called, please contact the TiDB team for help

1. BuildCastFunction build a cast CastStringAsString, and the fieldType is Enum.
2. compareFunctionClass.getFunction get fieldType Int and Enum, and set EnumSetAsInt flag, but not re-construct Cast function.
3. Get the final scalarFunction EQInt(1, CastStringAsString(Enum))). CastStringAsString can't get int value.
   BuildCastFunction is useless. See constant_fold.goL129. We should have the same behavior for all args.

Check List

Tests

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

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Fix panic for caseWhen function with enum type

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• ichn-hu
• lzmhhh123

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.

[ti-srebot]

/run-all-tests

[ti-srebot]

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

[tiancaiamao]

/merge

[ti-chi-bot]

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

Commit hash: 7a8bffe

[VelocityLight]

/merge

[ti-chi-bot]

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

Commit hash: 893e904fdd6fbb9b51829d0916d30c79dfa8f297

[tiancaiamao]

/merge

[ti-chi-bot]

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

Commit hash: 2adaf3c

[tiancaiamao]

CI seems to be failing, PTAL @wshwsh12

[wshwsh12]

Need #30011

[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.

[tiancaiamao]

/merge

[ti-chi-bot]

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

Commit hash: b0832a8