sql-mode: update compatibility#3192
Conversation
|
Note: mysql-compatibility.md is very different in versions below 4.0. You might need to resolve conflicts when this PR is cherry-picked to the lower versions. |
Yes, that's my plan :-) |
| + [Basic Features](/basic-features.md) | ||
| + Compatibility | ||
| + [MySQL Compatibility](/mysql-compatibility.md) | ||
| + [MySQL Compatibility](/mysql-compatibility.md) |
There was a problem hiding this comment.
In the future,maybe have other DB compatibility,so,i think just leave it as it is
There was a problem hiding this comment.
If that happens in the future, we update the TOC and change it back :-)
|
@zz-jason,Thanks for your review. |
|
|
||
| TiDB is fully compatible with the MySQL 5.7 protocol and the common features and syntax of MySQL 5.7. The ecosystem tools for MySQL 5.7 (PHPMyAdmin, Navicat, MySQL Workbench, mysqldump, and Mydumper/myloader) and the MySQL client can be used for TiDB. | ||
|
|
||
| However, some features of MySQL are not supported. This could be because there is now a better way to solve the problem (such as XML functions superceded by JSON), security issues (such as `SELECT INTO OUTFILE`), or a lack of current demand versus effort required (such as stored procedures and functions). Some features might also be difficult to implement as a distributed system. |
There was a problem hiding this comment.
select into outfile is supported in TiDB 4.0, we'd better not backport this PR to release 2.1, 3.0, and 3.1.
There was a problem hiding this comment.
Understood. The 2.1-3.0 docs will still say this feature is not supported (it's further down in the document). What is removed is an explanation of why we will not add certain features such as this one (which becomes confusing, since it was added in a later version).
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
cherry pick to release-2.1 in PR #3233 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
cherry pick to release-3.0 in PR #3234 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
cherry pick to release-3.1 in PR #3235 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
cherry pick to release-4.0 in PR #3236 |
* cherry pick #3192 to release-3.0 Signed-off-by: ti-srebot <ti-srebot@pingcap.com> * Update TOC.md * Update assign-by-files.yml * Delete assign-by-files.yml * Update mysql-compatibility.md Co-authored-by: Null not nil <67764674+nullnotnil@users.noreply.github.com>
What is changed, added or deleted? (Required)
Fixes #1768
Also addresses a minor issue in mysql-compatibility where in my #3151 I said that
SELECT INTO OUTFILEmay not be implemented, but it since has been.I also propose moving "Compatibility -> MySQL Compatibility" to "MySQL Compatibility" in the menu, to simplify navigation, and add myself as a reviewer to mysql compatibility areas.
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?