Account Management Statements •MySQL does not support the standard SQL  UNDER  privilege. •Standard SQL privileges are structured in a hierarchical manner. If you remove a user, all privileges the user has been granted are revoked. This is also true in MySQL if you use  DROP USER . See Section 13.7.1.5, “DROP USER Statement” . •In standard SQL, when you drop a table, all privileges for the table are revoked. In standard SQL, when you revoke a privilege, all privileges that were granted based on that privilege are also revoked. In MySQL, privileges can be dropped with  DROP USER  or  REVOKE  statements. •In MySQL, it is possible to have the  INSERT  privilege for only some of the columns in a table. In this case, you can still execute  INSERT  statements on the table, provided that you insert values only for those columns for which you have the  INSERT  privilege. The omitted columns are set to their implicit default values if strict SQL mode is not enabled. In strict mode, the statement is rejected if any of the omitted columns have no default value. (Standard SQL requires you to have the  INSERT  privilege on all columns.) For information about strict SQL mode and implicit default values, see Section 5.1.11, “Server SQL Modes” , and Section 11.6, “Data Type Default Values” . 2876 REVOKE priv_type  [( column_list )] [,  priv_type  [( column_list )]] ... ON [ object_type ]  priv_level FROM  user_or_role  [,  user_or_role ] ... 13.7.1.7 RENAME USER Statement 13.7.1.8 REVOKE Statement The privilege changes take effect as indicated in Section 6.2.13, “When Privilege Changes Take Effect” . RENAME USER  causes the privileges held by the old user to be those held by the new user. However, RENAME USER  does not automatically drop or invalidate databases or objects within them that the old user created. This includes stored programs or views for which the  DEFINER  attribute names the old user. Attempts to access such objects may produce an error if they execute in definer security context. (For information about security context, see Section 25.6, “Stored Object Access Control” .) The host name part of the account name, if omitted, defaults to  ’%’ . RENAME USER ’jeffrey’@’localhost’ TO ’jeff’@’127.0.0.1’; Each account name uses the format described in Section 6.2.4, “Specifying Account Names” . For example: As of MySQL 8.0.22,  RENAME USER  fails with an error if any account to be renamed is named as the DEFINER  attribute for any stored object. (That is, the statement fails if renaming an account would cause a stored object to become orphaned.) To perform the operation anyway, you must have the  SET_USER_ID privilege; in this case, the statement succeeds with a warning rather than failing with an error. For additional information, including how to identify which objects name a given account as the  DEFINER attribute, see Orphan Stored Objects. To use  RENAME USER , you must have the global  CREATE USER  privilege, or the  UPDATE  privilege for the mysql  system schema. When the  read_only  system variable is enabled,  RENAME USER  additionally requires the  CONNECTION_ADMIN  privilege (or the deprecated  SUPER  privilege). The  RENAME USER  statement renames existing MySQL accounts. An error occurs for old accounts that do not exist or new accounts that already exist. RENAME USER  old_user  TO  new_user [,  old_user  TO  new_user ] ...