Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the command and output in SQL statements #11807

Merged
merged 2 commits into from Dec 30, 2022

Conversation

Oreoxmt
Copy link
Collaborator

@Oreoxmt Oreoxmt commented Dec 29, 2022

Signed-off-by: Aolin aolin.zhang@pingcap.com

First-time contributors' checklist

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

  • master (the latest development version)
  • v6.6 (TiDB 6.6 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.4 (TiDB 6.4 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)
  • v5.3 (TiDB 5.3 versions)
  • v5.2 (TiDB 5.2 versions)
  • v5.1 (TiDB 5.1 versions)
  • v5.0 (TiDB 5.0 versions)

What is the related PR or file link(s)?

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

Signed-off-by: Aolin <aolin.zhang@pingcap.com>
@Oreoxmt Oreoxmt added type/enhancement This issue/PR improves documentation usability or supplements document content. translation/from-docs-cn This PR is translated from a PR in pingcap/docs-cn. area/sql-infra Indicates that the Issue or PR belongs to the area of sql-infra and sql-metadata. needs-cherry-pick-release-6.1 Should cherry pick this PR to release-6.1 branch. needs-cherry-pick-release-6.4 needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. labels Dec 29, 2022
@Oreoxmt Oreoxmt self-assigned this Dec 29, 2022
@ti-chi-bot
Copy link
Member

ti-chi-bot commented Dec 29, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • TomShawn

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Dec 29, 2022
Query OK, 0 rows affected (0.02 sec)
```

Jennifer no longer has the default role of analyticsteam associated, or can set the role to analyticsteam:
`jennifer` no longer has the default role of `analyticsteam` associated, or can set the role to `analyticsteam`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
`jennifer` no longer has the default role of `analyticsteam` associated, or can set the role to `analyticsteam`.
`jennifer` no longer has the default role of `analyticsteam` associated, nor can set the role to `analyticsteam`.


Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
Note that by default `jennifer` needs to `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Note that by default `jennifer` needs to `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:
Note that by default `jennifer` needs to execute `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:


Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and you do not have to execute the statement `SET ROLE`:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and you do not have to execute the statement `SET ROLE`:
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and `jennifer` does not have to execute the statement `SET ROLE`:

Copy link
Contributor

@TomShawn TomShawn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rest LGTM


Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
Note that by default `jennifer` needs to `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Note that by default `jennifer` needs to `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:
Note that by default `jennifer` needs to execute `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:


Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and you do not have to execute the statement `SET ROLE`:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and you do not have to execute the statement `SET ROLE`:
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and `jennifer` does not have to execute the statement `SET ROLE`:


Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
Note that by default `jennifer` needs to `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Note that by default `jennifer` needs to `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:
Note that by default `jennifer` needs to execute `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:


Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and you do not have to execute the statement `SET ROLE`:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and you do not have to execute the statement `SET ROLE`:
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and `jennifer` does not have to execute the statement `SET ROLE`:


Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
Note that by default `jennifer` needs to `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Note that by default `jennifer` needs to `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:
Note that by default `jennifer` needs to execute `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:


Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and you do not have to execute the statement `SET ROLE`:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and you do not have to execute the statement `SET ROLE`:
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and `jennifer` does not have to execute the statement `SET ROLE`:


Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
Note that by default `jennifer` needs to `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Note that by default `jennifer` needs to `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:
Note that by default `jennifer` needs to execute `SET ROLE analyticsteam` in order to be able to use the privileges associated with the `analyticsteam` role:


Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and you do not have to execute the statement `SET ROLE`:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and you do not have to execute the statement `SET ROLE`:
After this, the user `jennifer` has the privileges associated with the role `analyticsteam` and `jennifer` do not have to execute the statement `SET ROLE`:

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Dec 30, 2022
Signed-off-by: Aolin <aolin.zhang@pingcap.com>
@Oreoxmt Oreoxmt added the require-LGT1 Indicates that the PR requires an LGTM. label Dec 30, 2022
@Oreoxmt
Copy link
Collaborator Author

Oreoxmt commented Dec 30, 2022

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: 4b73978

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Dec 30, 2022
@ti-chi-bot ti-chi-bot merged commit 4b29c51 into pingcap:master Dec 30, 2022
@ti-chi-bot
Copy link
Member

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

@ti-chi-bot
Copy link
Member

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

@ti-chi-bot
Copy link
Member

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

@Oreoxmt Oreoxmt deleted the translate/docs-cn-12268 branch February 14, 2023 08:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/sql-infra Indicates that the Issue or PR belongs to the area of sql-infra and sql-metadata. needs-cherry-pick-release-6.1 Should cherry pick this PR to release-6.1 branch. needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. require-LGT1 Indicates that the PR requires an LGTM. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1. translation/from-docs-cn This PR is translated from a PR in pingcap/docs-cn. type/enhancement This issue/PR improves documentation usability or supplements document content.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants