planner: return an error when using prepared protocol with select-into statement (#49357)

[ti-chi-bot]

This is an automated cherry-pick of #49357

What problem does this PR solve?

Issue Number: close #49166

Problem Summary: planner: return an error when using prepared protocol with select-into statement

What changed and how does it work?

Limited by the current implementation, prepared protocol cannot support select-into statements, otherwise might cause some wrong results, return an error directly in this case.

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

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (release-7.5@cf7a0af). Click here to learn what that means.
The diff coverage is 100.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.5     #49365   +/-   ##
================================================
  Coverage               ?   74.3349%           
================================================
  Files                  ?       1404           
  Lines                  ?     426078           
  Branches               ?          0           
================================================
  Hits                   ?     316725           
  Misses                 ?      90248           
  Partials               ?      19105           

Flag	Coverage Δ
unit	74.3349% <100.0000%> (?)

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

Components	Coverage Δ
dumpling	53.9913% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	54.0158% <0.0000%> (?)

[fixdb]

+1

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [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-02-20 04:05:28.135969699 +0000 UTC m=+330016.883592810: ☑️ agreed by fixdb.
• 2024-02-20 04:18:37.478710953 +0000 UTC m=+330806.226334049: ☑️ agreed by qw4990.

[qw4990]

/test check_dev_2

[ti-chi-bot]

@qw4990: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test pull-br-integration-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/release-7.5/ghpr_build
• pingcap/tidb/release-7.5/ghpr_check
• pingcap/tidb/release-7.5/ghpr_check2
• pingcap/tidb/release-7.5/ghpr_mysql_test
• pingcap/tidb/release-7.5/ghpr_unit_test

In response to this:

/test check_dev_2

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/test-infra repository.

[qw4990]

/test check-dev2

[tiprow]

@qw4990: No presubmit jobs available for pingcap/tidb@release-7.5

In response to this:

/test check_dev_2

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/test-infra repository.

[tiprow]

@qw4990: No presubmit jobs available for pingcap/tidb@release-7.5

In response to this:

/test check-dev2

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/test-infra repository.

[qw4990]

/test mysql-test

[tiprow]

@qw4990: No presubmit jobs available for pingcap/tidb@release-7.5

In response to this:

/test mysql-test

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/test-infra repository.

[qw4990]

/test check-dev2

[tiprow]

@qw4990: No presubmit jobs available for pingcap/tidb@release-7.5

In response to this:

/test check-dev2

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/test-infra repository.

[qw4990]

/retest

[qw4990]

/retest

[qw4990]

/retest

[qw4990]

/retest

[qw4990]

/retest

[qw4990]

/test check-dev2

[tiprow]

@qw4990: No presubmit jobs available for pingcap/tidb@release-7.5

In response to this:

/test check-dev2

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/test-infra repository.

[ti-chi-bot]

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be approved by the approvers firstly.
2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

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/test-infra repository.