planner: fix wrong schema when to solve the schema name in CTE

[hawkingrei]

What problem does this PR solve?

Issue Number: close #54582

Problem Summary:

What changed and how does it work?

when to adjustCTEPlanOutputName, we will force the current db name as the query schema. but it is the root cause. sometime query will set specific schema name. we must follow this name to get meta.

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 wrong schema when to solve the schema name in CTE

修复在CTE中解析数据库名时，得到错误的数据库名

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.7122%. Comparing base (f973f19) to head (cab723e).
Report is 8 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #57253        +/-   ##
================================================
+ Coverage   72.9101%   73.7122%   +0.8021%     
================================================
  Files          1669       1669                
  Lines        461114     462615      +1501     
================================================
+ Hits         336199     341004      +4805     
+ Misses       104270     101063      -3207     
+ Partials      20645      20548        -97     

Flag	Coverage Δ
integration	43.6303% <100.0000%> (?)
unit	72.5461% <100.0000%> (+0.2625%)	⬆️

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

Components	Coverage Δ
dumpling	52.7673% <ø> (ø)
parser	∅ <ø> (∅)
br	45.1457% <ø> (+0.0401%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, winoros

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/planner/OWNERS [AilinKid,winoros]

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-12 12:36:12.403132927 +0000 UTC m=+359734.594001916: ☑️ agreed by winoros.
• 2024-11-12 13:59:58.466928009 +0000 UTC m=+364760.657797007: ☑️ agreed by AilinKid.

[hawkingrei]

/test all

[tiprow]

@hawkingrei: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	cab723e	link	true	/test fast_test_tiprow

Full PR test history. Your PR dashboard.

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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