Account Management Statements Each account name uses the format described in Section 6.2.4, “Specifying Account Names” . For example: The host name part of the account name, if omitted, defaults to  ’%’ . DROP USER  does not automatically close any open user sessions. Rather, in the event that a user with an open session is dropped, the statement does not take effect until that user’s session is closed. Once the session is closed, the user is dropped, and that user’s next attempt to log in fails.  This is by design . DROP 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 dropped 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” .) 2863 13.7.1.6 GRANT Statement Important DROP USER ’jeffrey’@’localhost’; GRANT priv_type  [( column_list )] [,  priv_type  [( column_list )]] ... ON [ object_type ]  priv_level TO  user_or_role  [,  user_or_role ] ... [WITH GRANT OPTION] [AS  user [WITH ROLE DEFAULT | NONE | ALL | ALL EXCEPT  role  [,  role  ] ... |  role  [,  role  ] ... ] ] } GRANT PROXY ON  user_or_role TO  user_or_role  [,  user_or_role ] ... [WITH GRANT OPTION] GRANT  role  [,  role ] ... TO  user_or_role  [,  user_or_role ] ... [WITH ADMIN OPTION] object_type : { TABLE | FUNCTION | PROCEDURE } priv_level : { * | *.* |  db_name .* |  db_name.tbl_name |  tbl_name |  db_name . routine_name } user_or_role : { user  (see Section 6.2.4, “Specifying Account Names” ) |  role  (see Section 6.2.5, “Specifying Role Names” ) }