planner: fix cannot binding for deleting multi table with alias

[hawkingrei]

What problem does this PR solve?

Issue Number: close #56726

Problem Summary:

What changed and how does it work?

delete tt1 from t1 tt1,(select max(id) id from t2)tt2 where tt1.id<=tt2.id
delete tt1 will be transfer to delete current_database.t1 in default when to deal with the statsment in the create binding.
because tt1 cannot be used as alias in delete statement.
so we have to set tt1 as alias by aliasChecker.

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.

fix cannot binding for deleting multi table with alias

修复无法为带别名的多表删除进行 binding 的问题

[hawkingrei]

/retest

[codecov]

Codecov Report

Attention: Patch coverage is 94.59459% with 2 lines in your changes missing coverage. Please review.

Project coverage is 73.4985%. Comparing base (3c70a28) to head (efe464f).
Report is 3 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #57255        +/-   ##
================================================
+ Coverage   72.8888%   73.4985%   +0.6096%     
================================================
  Files          1672       1672                
  Lines        462231     462307        +76     
================================================
+ Hits         336915     339789      +2874     
+ Misses       104562     101842      -2720     
+ Partials      20754      20676        -78     

Flag	Coverage Δ
integration	43.4020% <75.0000%> (?)
unit	72.3046% <94.5945%> (+0.0382%)	⬆️

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

Components	Coverage Δ
dumpling	52.7673% <ø> (ø)
parser	∅ <ø> (∅)
br	45.1379% <ø> (-0.0031%)	⬇️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qw4990, tangenta

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:

• pkg/parser/OWNERS [tangenta]
• pkg/planner/OWNERS [qw4990]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-11-15 07:42:35.820544997 +0000 UTC m=+601318.011413987: ☑️ agreed by tangenta.
• 2024-11-15 08:50:09.145173889 +0000 UTC m=+605371.336042881: ☑️ agreed by qw4990.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.5: #57419.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #57420.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #57421.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #57422.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #57423.