executor, infoschema: filter out the PRIMARY index and foreign keys in table_constraints

[YangKeao]

What problem does this PR solve?

Issue Number: close #55253
Problem Summary:

The previous patch https://github.com/pingcap/tidb/pull/55236/files#diff-cd85979e0fe90c288bf582cb1b181f51cbb7b874423cc4e1163617e2dbf95c98R2140-R2142 forgot to filter the PRIMARY index and the foreign keys. This PR fixes this issue.

What changed and how does it work?

Add two filters condition on PRIMARY index and foreign keys.

It'd be better to have a function to automatically check all records according to the extracted column and defined columns in the table, and replace all manual append(rows, record). However, @tangenta told me he's working on rewriting the extractor and making every table has its own retriever, so I only submit some temporary fixes.

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.

Release note

Fix the issue that the `PRIMARY` index cannot be filtered out from the `TABLE_CONSTRAINTS` table.

[YangKeao]

/hold Wait a minute. I'm checking the tests.

[codecov]

Codecov Report

Attention: Patch coverage is 91.11111% with 4 lines in your changes missing coverage. Please review.

Project coverage is 74.8320%. Comparing base (3dfa15c) to head (fba6f4b).
Report is 45 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55255        +/-   ##
================================================
+ Coverage   72.8486%   74.8320%   +1.9833%     
================================================
  Files          1570       1573         +3     
  Lines        439518     442229      +2711     
================================================
+ Hits         320183     330929     +10746     
+ Misses        99610      90973      -8637     
- Partials      19725      20327       +602     

Flag	Coverage Δ
integration	49.1127% <80.0000%> (?)
unit	71.8212% <91.1111%> (-0.0666%)	⬇️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	52.5521% <ø> (+6.6900%)	⬆️

[YangKeao]

/unhold

[YangKeao]

/test pull-integration-common-test

[YangKeao]

/test pull-integration-nodejs-test

[tiprow]

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

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test pull-integration-common-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-sigs/prow repository.

[tiprow]

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

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test pull-integration-nodejs-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-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [tangenta,tiancaiamao]

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-08-07 13:01:50.075201822 +0000 UTC m=+443439.942300909: ☑️ agreed by tangenta.
• 2024-08-12 06:01:09.16067554 +0000 UTC m=+161353.864145231: ☑️ agreed by tiancaiamao.