utf8mb4, ascii, latin1 and binary • SYS schema • Optimizer trace • XML Functions • X-Protocol #1109 • Savepoints #6840 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit internally, but SELECT * FROM t1; Empty set (0.01 sec) 12.11.2.70.3 MySQL compatibility • TiDB does not support savepoints or the syntax ROLLBACK TO SAVEPOINT. 1768 • TiDB parses but ignores the syntax ROLLBACK AND [NO] --------------+------+------------+ �→ | Engine | Support | Comment | �→ Transactions | XA | Savepoints | +-- �→ ------+---------+------------------------------------------------------------+-----

utf8mb4, ascii, latin1 and binary • SYS schema • Optimizer trace • XML Functions • X-Protocol #1109 • Savepoints #6840 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit internally, but SELECT * FROM t1; Empty set (0.01 sec) 12.11.2.74.3 MySQL compatibility • TiDB does not support savepoints or the syntax ROLLBACK TO SAVEPOINT. • TiDB parses but ignores the syntax ROLLBACK AND [NO] RELEASE --------------+------+------------+ �→ | Engine | Support | Comment | �→ Transactions | XA | Savepoints | +-- �→ ------+---------+------------------------------------------------------------+-----

utf8mb4, ascii, latin1 and binary • SYS schema • Optimizer trace • XML Functions • X-Protocol #1109 • Savepoints #6840 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit internally, but SELECT * FROM t1; Empty set (0.01 sec) 12.11.2.70.3 MySQL compatibility • TiDB does not support savepoints or the syntax ROLLBACK TO SAVEPOINT. 1831 • TiDB parses but ignores the syntax ROLLBACK AND [NO] --------------+------+------------+ �→ | Engine | Support | Comment | �→ Transactions | XA | Savepoints | +-- �→ ------+---------+------------------------------------------------------------+-----

binary, utf8, utf8mb4, and gbk. • SYS schema • Optimizer trace • XML Functions • X-Protocol #1109 • Savepoints #6840 • Column-level privileges #9766 • XA syntax (TiDB uses a two-phase commit internally, but SELECT * FROM t1; Empty set (0.01 sec) 12.11.2.74.3 MySQL compatibility • TiDB does not support savepoints or the syntax ROLLBACK TO SAVEPOINT. • TiDB parses but ignores the syntax ROLLBACK AND [NO] RELEASE --------------+------+------------+ �→ | Engine | Support | Comment | �→ Transactions | XA | Savepoints | +-- �→ ------+---------+------------------------------------------------------------+-----

ascii/latin1/binary/utf8/utf8mb4 的字符集 • SYS schema • MySQL 追踪优化器 • XML 函数 • X-Protocol #1109 • Savepoints #6840 • 列级权限 #9766 • XA 语法（TiDB 内部使用两阶段提交，但并没有通过 SQL 接口公开） • CREATE TABLE tblName AS SELECT -------------+------+------------+ �→ | Engine | Support | Comment | Transactions | �→ XA | Savepoints | +--------+---------+------------------------------------------------------------+---------- NULL | | | TRANSACTIONS | varchar(3) | YES | | NULL | | | XA | varchar(3) | YES | | NULL | | | SAVEPOINTS | varchar(3) | YES | | NULL | | +--------------+-------------+------+------+---------+-------+

ascii/latin1/binary/utf8/utf8mb4 的字符集 • SYS schema • MySQL 追踪优化器 • XML 函数 • X-Protocol #1109 • Savepoints #6840 • 列级权限 #9766 • XA 语法（TiDB 内部使用两阶段提交，但并没有通过 SQL 接口公开） • CREATE TABLE tblName AS SELECT -------------+------+------------+ �→ | Engine | Support | Comment | Transactions | �→ XA | Savepoints | +--------+---------+------------------------------------------------------------+---------- NULL | | | TRANSACTIONS | varchar(3) | YES | | NULL | | | XA | varchar(3) | YES | | NULL | | | SAVEPOINTS | varchar(3) | YES | | NULL | | +--------------+-------------+------+------+---------+-------+

Data changes made to the table data after the savepoint will be reverted in the rollback, and all savepoints after the savepoint are deleted. In a pessimistic transaction, the locks held by the transaction SAVEPOINT identifier does not exist • RELEASE SAVEPOINT statement removes the named savepoint and all savepoints after this savepoint from the current transaction, without committing or rolling back the current (42000): SAVEPOINT identifier does not exist After the transaction is committed or rolled back, all savepoints in the transaction will be deleted. 14.11.2.80.1 Examples Create a table t1: CREATE TABLE t1

ascii/latin1/binary/utf8/utf8mb4 的字符集 • SYS schema • MySQL 追踪优化器 • XML 函数 • X-Protocol #1109 • Savepoints #6840 • 列级权限 #9766 • XA 语法（TiDB 内部使用两阶段提交，但并没有通过 SQL 接口公开） • CREATE TABLE tblName AS SELECT -------------+------+------------+ �→ | Engine | Support | Comment | Transactions | �→ XA | Savepoints | +--------+---------+------------------------------------------------------------+---------- NULL | | | TRANSACTIONS | varchar(3) | YES | | NULL | | | XA | varchar(3) | YES | | NULL | | | SAVEPOINTS | varchar(3) | YES | | NULL | | +--------------+-------------+------+------+---------+-------+

binary, utf8, utf8mb4, and gbk. • SYS schema • Optimizer trace • XML Functions • X-Protocol #1109 • Savepoints #6840 • Column-level privileges #9766 103 • XA syntax (TiDB uses a two-phase commit internally SELECT * FROM t1; Empty set (0.01 sec) 14.11.2.76.3 MySQL compatibility • TiDB does not support savepoints or the syntax ROLLBACK TO SAVEPOINT. • TiDB parses but ignores the syntax ROLLBACK AND [NO] RELEASE --------------+------+------------+ �→ | Engine | Support | Comment | �→ Transactions | XA | Savepoints | +-- �→ ------+---------+------------------------------------------------------------+-----

Data changes made to the table data after the savepoint will be reverted in the rollback, and all savepoints after the savepoint are deleted. In a pessimistic transaction, the locks held by the transaction SAVEPOINT identifier does not exist • RELEASE SAVEPOINT statement removes the named savepoint and all savepoints after this savepoint from the current transaction, without committing or rolling back the current (42000): SAVEPOINT identifier does not exist After the transaction is committed or rolled back, all savepoints in the transaction will be deleted. 14.11.2.84.1 Examples Create a table t1: CREATE TABLE t1