parser: Accept PASSWORD REQUIRE CURRENT DEFAULT

[dveeden]

What problem does this PR solve?

Issue Number: close #53305

Problem Summary:

1. This only accepts CREATE USER ... PASSWORD REQUIRE CURRENT DEFAULT. It doesn't support PASSWORD REQUIRE CURRENT OPTIONAL.
2. This isn't stored, checked or validated.

What changed and how does it work?

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.

TiDB now accepts `PASSWORD REQUIRE CURRENT DEFAULT` as part of `CREATE USER` to aid MySQL 8.0 compatibility

[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-sigs/prow repository.

[dveeden]

/ok-to-test

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.2115%. Comparing base (afd2343) to head (896921a).
Report is 25 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #53306        +/-   ##
================================================
+ Coverage   72.5370%   75.2115%   +2.6744%     
================================================
  Files          1506       1507         +1     
  Lines        430741     435622      +4881     
================================================
+ Hits         312447     327638     +15191     
+ Misses        98968      88192     -10776     
- Partials      19326      19792       +466     

Flag	Coverage Δ
integration	50.0484% <ø> (?)
unit	71.9804% <ø> (+0.4509%)	⬆️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	50.4280% <ø> (+8.6228%)	⬆️

[CbcWestwolf]

LGTM

[lastincisor]

LGTM

[ti-chi-bot]

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

In response to this:

LGTM

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]

cc @yudongusa @easonn7

[ti-chi-bot]

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

In response to this:

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.

[ljun0712]

LGTM（This PR is only for syntax compatibility with MySQL.）

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-05-16 02:18:56.928392048 +0000 UTC m=+1706090.685527620: ☑️ agreed by CbcWestwolf.
• 2024-05-29 10:16:29.527691267 +0000 UTC m=+2857943.284826840: ☑️ agreed by tangenta.

[easonn7]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CbcWestwolf, easonn7, lastincisor, ljun0712, 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:

• OWNERS [CbcWestwolf,tangenta]
• pkg/parser/OWNERS [easonn7,tangenta]

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]

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