mysql-compatibility: Improve MySQL Compatibility (#3151)#3174
Merged
3 commits merged intoJul 6, 2020
Merged
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
5 tasks
ti-srebot
added
contribution
lilin90
reviewed
Jul 6, 2020
|
The difference between dev and 4.0, was that 4.0 still had a line about invisible indexes (added in master). Because this is an 8.0 feature anyway, it doesn't need to be documented in mysql-compatibility, which claims only 5.7 compatibility. |
Contributor
Author
|
@lilin90,Thanks for your review. |
ghost
merged commit 
This pull request was closed.
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
2 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.
cherry-pick #3151 to release-4.0
What is changed, added or deleted? (Required)
This improves some aspects of describing MySQL compatibility.
I thought it was important to point to GitHub issues on some of the more common feature requests, and explain in more detailed context than ROI why some features may not be available.
The DDL section was hard to read, so I reformatted it to focus on what was missing versus what was supported.
The ANALYZE TABLE update fixes #2478
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
fixes #2478 + some additional changes.