From 921402b227818188e54e4c8f01d2d9fad0297519 Mon Sep 17 00:00:00 2001 From: doc-claw-bot Date: Fri, 4 Sep 2026 13:21:49 +0000 Subject: [PATCH] sql: note unsupported GRANT PROXY in compatibility --- sql-statements/sql-statement-grant-privileges.md | 1 + 1 file changed, 1 insertion(+) diff --git a/sql-statements/sql-statement-grant-privileges.md b/sql-statements/sql-statement-grant-privileges.md index 5dfa733f90c4b..bfb470e359019 100644 --- a/sql-statements/sql-statement-grant-privileges.md +++ b/sql-statements/sql-statement-grant-privileges.md @@ -82,6 +82,7 @@ mysql> SHOW GRANTS FOR 'newuser'; ## MySQL compatibility * Similar to MySQL, the `USAGE` privilege denotes the ability to log into a TiDB server. +* Unlike MySQL, TiDB does not support `GRANT PROXY`. * Starting from v8.5.6, TiDB supports a MySQL-compatible column-level privilege management mechanism. You can grant or revoke `SELECT`, `INSERT`, `UPDATE`, and `REFERENCES` privileges on specific columns in a specified table. For more information, see [Column-Level Privilege Management](/column-privilege-management.md). * Similar to MySQL, when the `NO_AUTO_CREATE_USER` sql mode is not present, the `GRANT` statement will automatically create a new user with an empty password when a user does not exist. Removing this sql-mode (it is enabled by default) presents a security risk. * In TiDB, after the `GRANT ` statement is executed successfully, the execution result takes effect immediately on the current connection. Whereas [in MySQL, for some privileges, the execution results take effect only on subsequent connections](https://dev.mysql.com/doc/refman/8.0/en/privilege-changes.html). See [TiDB #39356](https://github.com/pingcap/tidb/issues/39356) for details.