MySQL are not supported. This could be because there is now a better way to solve the problem (such as XML functions superseded by JSON), or a lack of current demand versus effort required (such as stored procedures Character sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. • SYS schema • Optimizer trace • XML Functions • X-Protocol #1109 • Savepoints #6840 • Column-level privileges #9766 103 • XA syntax (TiDB tree for this example project is shown below (some incomprehensible parts are removed): . ￿── pom.xml ￿── src ￿── main ￿── java ￿ ￿── com ￿ ￿── pingcap ￿ ￿── App.java ￿ ￿── controller 179 ￿ ￿

Workbench、mysqldump、Mydumper/Myloader）、客户端等均适用于 TiDB。 但 TiDB 尚未支持一些 MySQL 功能，可能的原因如下： • 有更好的解决方案，例如 JSON 取代 XML 函数。 • 目前对这些功能的需求度不高，例如存储流程和函数。 • 一些功能在分布式系统上的实现难度较大。 除此以外，TiDB 不支持 MySQL 复制协议，但提供了专用工具用于与 MySQL GIS/GEOMETRY）、数据类型和索引 #6347 • 非 ascii、latin1、binary、utf8、utf8mb4、gbk 的字符集 • SYS schema • MySQL 追踪优化器 • XML 函数 • X-Protocol #1109 • Savepoints #6840 • 列级权限 #9766 • XA 语法（TiDB 内部使用两阶段提交，但并没有通过 SQL 接口公开） false 4.3.2.7 实现细节 本小节介绍示例应用程序项目中的组件。 4.3.2.7.1 总览 本示例项目的大致目录树如下所示（删除了有碍理解的部分）： . ├ ─ ─ pom.xml └ ─ ─ src └ ─ ─ main ├ ─ ─ java │ └ ─ ─ com │ └ ─ ─ pingcap │ ├ ─ ─ App.java │ ├ ─ ─ controller

MySQL are not supported. This could be because there is now a better way to solve the problem (such as XML functions superseded by JSON), or a lack of current demand versus effort required (such as stored procedures Character sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. • SYS schema • Optimizer trace • XML Functions • X-Protocol #1109 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit mybatis-quickstart repository. Connect to TiDB Edit the MyBatis configuration file mybatis-config.xml: xml version="1.0" encoding="UTF-8" ?>

could be because there is now a better way to solve the problem (such as the use of JSON instead of XML functions) or a lack of current demand versus effort required (such as stored procedures and functions) Character sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. • SYS schema • Optimizer trace • XML Functions • X-Protocol #1109 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit mybatis-quickstart repository. Connect to TiDB Edit the MyBatis configuration file mybatis-config.xml: xml version="1.0" encoding="UTF-8" ?>

could be because there is now a better way to solve the problem (such as the use of JSON instead of XML functions) or a lack of current demand versus effort required (such as stored procedures and functions) Character sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. • SYS schema • Optimizer trace • XML Functions 88 • X-Protocol #1109 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase mybatis-quickstart repository. Connect to TiDB Edit the MyBatis configuration file mybatis-config.xml: 141 xml version="1.0" encoding="UTF-8" ?>

could be because there is now a better way to solve the problem (such as the use of JSON instead of XML functions) or a lack of current demand versus effort required (such as stored procedures and functions) Character sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. • SYS schema • Optimizer trace • XML Functions 75 • X-Protocol #1109 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase mybatis-quickstart repository. Connect to TiDB Edit the MyBatis configuration file mybatis-config.xml: xml version="1.0" encoding="UTF-8" ?>

could be because there is now a better way to solve the problem (such as the use of JSON instead of XML functions) or a lack of current demand versus effort required (such as stored procedures and functions) #6347 • Character sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. • Optimizer trace • XML Functions • X-Protocol #1109 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit mybatis-quickstart repository. Connect to TiDB Edit the MyBatis configuration file mybatis-config.xml: xml version="1.0" encoding="UTF-8" ?>

could be because there is now a better way to solve the problem (such as the use of JSON instead of XML functions) or a lack of current demand versus effort required (such as stored procedures and functions) #6347 • Character sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. • Optimizer trace • XML Functions • X-Protocol #1109 103 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase mybatis-quickstart repository. Connect to TiDB Edit the MyBatis configuration file mybatis-config.xml: xml version="1.0" encoding="UTF-8" ?>

could be because there is now a better way to solve the problem (such as the use of JSON instead of XML functions) or a lack of current demand versus effort required (such as stored procedures and functions) #6347 • Character sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. • Optimizer trace • XML Functions • X-Protocol #1109 108 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase mybatis-quickstart repository. Connect to TiDB Edit the MyBatis configuration file mybatis-config.xml: xml version="1.0" encoding="UTF-8" ?>

could be because there is now a better way to solve the problem (such as the use of JSON instead of XML functions) or a lack of current demand versus effort required (such as stored procedures and functions) #6347 • Character sets other than ascii, latin1, binary, utf8, utf8mb4, and gbk. • Optimizer trace • XML Functions • X-Protocol #1109 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit mybatis-quickstart repository. Connect to TiDB Edit the MyBatis configuration file mybatis-config.xml: xml version="1.0" encoding="UTF-8" ?>