sql: add explanation for different versions#2076
Merged
Merged
Conversation
toutdesuite
added
needs-cherry-pick-3.0
translation/from-docs-cn
yikeke
reviewed
Mar 24, 2020
| ## MySQL compatibility | ||
|
|
||
| This statement is understood to be fully compatible with MySQL. Any compatibility differences should be [reported via an issue](/report-issue.md) on GitHub. | ||
| For TiDB 2.0, you can use the `USE` statement to access any database. For TiDB 3.0 or later versions, it checks whether you have access to the database when using the `USE` statement. This statement is understood to be fully compatible with MySQL. Any compatibility differences should be [reported via an issue](/report-issue.md) on GitHub. |
Contributor
There was a problem hiding this comment.
Suggested change
| For TiDB 2.0, you can use the `USE` statement to access any database. For TiDB 3.0 or later versions, it checks whether you have access to the database when using the `USE` statement. This statement is understood to be fully compatible with MySQL. Any compatibility differences should be [reported via an issue](/report-issue.md) on GitHub. | |
| In TiDB 2.0 versions, you can use `USE` statements to access any database. In TiDB 3.0 or later versions, TiDB checks whether you have the privilege to access the database when you use `USE` statements. | |
| Currently, `USE` statements are understood to be fully compatible with MySQL. Any compatibility differences should be [reported via an issue](/report-issue.md) on GitHub. |
Contributor
|
PTAL @imtbkcat |
yikeke
added
the
status/can-merge
Contributor
|
Your auto merge job has been accepted, waiting for 1931 |
Contributor
|
/run-all-tests |
Contributor
|
cherry pick to release-3.0 in PR #2092 |
sre-bot
pushed a commit
to sre-bot/docs
that referenced
this pull request
Mar 25, 2020
4 tasks
Contributor
|
cherry pick to release-3.1 in PR #2093 |
sre-bot
added a commit
that referenced
this pull request
Mar 25, 2020
sre-bot
added a commit
that referenced
this pull request
Mar 25, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is changed, added or deleted? (Required)
Explain a problem which may take attention on upgrade
Which TiDB version(s) do your changes apply to? (Required)
If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.
What is the related PR or file link(s)?