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
Conversation
Signed-off-by: Aolin <aolin.zhang@pingcap.com>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
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`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`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: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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`: |
There was a problem hiding this 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: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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`: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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`: |
Signed-off-by: Aolin <aolin.zhang@pingcap.com>
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 4b73978
|
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
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.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?