planner: change more conditions that are always false to dual | tidb-test=pr/2466

[hawkingrei]

What problem does this PR solve?

Issue Number: close #51446
Problem Summary:

What changed and how does it work?

During the logic optimization phase, we rely on Conds2TableDual to transform conditions that are always false into dual ones. However, the previous implementation was overly simplistic, so we have added some new judgments.

Check List

Tests

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

  • I checked and no code files have been changed.

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

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

None

[elsa0520]

Please change the title of PR.
This is not create a new rule. Just put the evaluate expression in the predicate push down rule

[elsa0520]

It seems that this function does not belong to logical_join. It shouldn't belong to any logical operator.
It should belong to expression utils.
Could we move it to right place ?

[hawkingrei]

I have create new file and move it into new file.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.5825%. Comparing base (fc8bdb5) to head (b61a842).
Report is 10 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59199        +/-   ##
================================================
+ Coverage   73.0496%   73.5825%   +0.5328%     
================================================
  Files          1689       1690         +1     
  Lines        466978     468288      +1310     
================================================
+ Hits         341126     344578      +3452     
+ Misses       104890     102710      -2180     
- Partials      20962      21000        +38     

Flag	Coverage Δ
integration	42.8464% <92.3076%> (?)
unit	72.2956% <100.0000%> (+0.0639%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	45.4774% <ø> (+0.0516%)	⬆️

[hawkingrei]

Please change the title of PR. This is not create a new rule. Just put the evaluate expression in the predicate push down rule

I have updated it.

[hawkingrei]

@AilinKid @elsa0520 PTAL

[AilinKid]

sgtm

[elsa0520]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-02-07 05:14:19.484555035 +0000 UTC m=+421531.016967034: ☑️ agreed by AilinKid.
• 2025-02-07 07:42:06.177139575 +0000 UTC m=+430397.709551572: ☑️ agreed by elsa0520.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, elsa0520, XuHuaiyu

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [AilinKid,XuHuaiyu,elsa0520]
• pkg/expression/OWNERS [XuHuaiyu]
• pkg/planner/OWNERS [AilinKid,elsa0520]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment