infoschema,executor: Add CHECK_CONSTRAINTS I_S table

[dveeden]

What problem does this PR solve?

• This adds the information_schema.CHECK_CONSTRAINTS table similar to what MySQL 8.0 does.

Note that other databases implement this as well:

postgres=# \d information_schema.CHECK_CONSTRAINTS
                       View "information_schema.check_constraints"
       Column       |               Type                | Collation | Nullable | Default 
--------------------+-----------------------------------+-----------+----------+---------
 constraint_catalog | information_schema.sql_identifier |           |          | 
 constraint_schema  | information_schema.sql_identifier |           |          | 
 constraint_name    | information_schema.sql_identifier |           |          | 
 check_clause       | information_schema.character_data |           |          | 

postgres=# SELECT VERSION();
                                                      version                                                      
-------------------------------------------------------------------------------------------------------------------
 PostgreSQL 15.3 (Debian 15.3-0+deb12u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
(1 row)

Issue Number: close #46427

Problem Summary:

What is changed and how it works?

Check List

Tests

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

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.

The `information_schema.CHECK_CONSTRAINTS` table was added for improved compatibility with MySQL 8.0

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[dveeden]

/test all

[tiprow]

Hi @dveeden. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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]

@dveeden: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test all

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.

[dveeden]

/ok-to-test

[codecov]

Codecov Report

Merging #46428 (7eb2838) into master (2f2bc41) will decrease coverage by 0.7364%.
Report is 131 commits behind head on master.
The diff coverage is 90.9090%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #46428        +/-   ##
================================================
- Coverage   73.4051%   72.6687%   -0.7364%     
================================================
  Files          1295       1340        +45     
  Lines        393760     402170      +8410     
================================================
+ Hits         289040     292252      +3212     
- Misses        86355      91372      +5017     
- Partials      18365      18546       +181     

Flag	Coverage Δ
integration	27.8703% <0.0000%> (?)
unit	73.2847% <90.9090%> (-0.1204%)	⬇️

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

Components	Coverage Δ
dumpling	54.0444% <ø> (ø)
parser	84.9805% <ø> (-0.0828%)	⬇️
br	48.1187% <ø> (-4.2017%)	⬇️

📢 Have feedback on the report? [Share it here](https://about.codecov.io/codecov-pr-comment-feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pingcap).

[purelind]

/test pull-integration-prisma-test

[tiprow]

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

• /test tiprow_fast_test

Use /test all to run all jobs.

In response to this:

/test pull-integration-prisma-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.

[Mini256]

LGTM, the Prisma Integration Test passed again.

https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftidb%2Fpull_integration_prisma_test/detail/pull_integration_prisma_test/2/

[ti-chi-bot]

@Mini256: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

LGTM, the Prisma Integration Test passed again.

https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftidb%2Fpull_integration_prisma_test/detail/pull_integration_prisma_test/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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fzzf678, Mini256, mjonss

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 [mjonss]

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:

• 2023-08-28 08:22:45.580410874 +0000 UTC m=+1742530.129426861: ☑️ agreed by mjonss.
• 2023-09-08 06:54:58.784557574 +0000 UTC m=+2687663.333573560: ☑️ agreed by fzzf678.

[dveeden]

/retest