Description of permission fields in the Mysql User table

I believe that the Mysql User table will not be unfamiliar to anyone. The following describes the permission fields of the Mysql User table for your reference. I hope this will help you learn about the Mysql User table.

Select_priv. Determine whether the user can SELECT data using the SELECT command.
Insert_priv. Determine whether the user can INSERT data using the INSERT command.
Update_priv. Determine whether the user can use the UPDATE command to modify existing data.
Delete_priv. Determine whether the user can use the DELETE command to DELETE existing data.
Create_priv. Determine whether users can create new databases and tables.
Drop_priv. Determine whether the user can delete existing databases and tables.
Reload_priv. Determine whether the user can execute specific commands used to refresh and reload MySQL internal cache, including logs, permissions, hosts, queries, and tables.
Shutdown_priv. Determine whether the user can shut down the MySQL server. Exercise caution when giving this permission to any user other than the root account.
Process_priv. Determine whether the user can view the processes of other users through the show processlist command.
File_priv. Determine whether the user can execute the select into outfile and load data infile commands.
Grant_priv. Determine whether the user can grant other users the permissions granted to the user. For example, if a user can insert, select, and delete information in the foo database and GRANT the GRANT permission, the user can GRANT any or all of its permissions to any other user in the system.
References_priv. Currently, it is only a placeholder for some future functions.
Index_priv. Determine whether you can create or delete table indexes.
Alter_priv. Determine whether the user can rename or modify the table structure.
Show_db_priv. Determine whether the user can view the names of all databases on the server, including databases with sufficient access permissions. You can consider disabling this permission for all users, unless there is a particularly irresistible reason.
Super_priv. Determine whether the user can execute some powerful management functions, such as using the KILL command to delete user processes, using set global to modify GLOBAL MySQL variables, and executing commands on replication and logs.
Create_tmp_table_priv. Determine whether the user can create a temporary table.
Lock_tables_priv. Determine whether you can use the lock tables command to block Table Access/modification.
Execute_priv. Determine whether the user can execute the stored procedure. This permission is valid only in MySQL 5.0 and later versions.
Repl_slave_priv. Determine whether the user can read binary log files used to maintain the replication database environment. This user is located in the main system, facilitating communication between the host and the client.
Repl_client_priv. Determine whether the user can determine the location of the replication slave server and master server.
Create_view_priv. Determine whether a user can create a view. This permission is valid only in MySQL 5.0 and later versions. For more information about views, see Chapter 34th.
Show_view_priv. Determine whether the user can view the view or understand how the view is executed. This permission is valid only in MySQL 5.0 and later versions. For more information about views, see Chapter 34th.
Create_routine_priv. Determine whether the user can change or discard stored procedures and functions. This permission is introduced in MySQL 5.0.
Alter_routine_priv. Determine whether users can modify or delete storage functions and functions. This permission is introduced in MySQL 5.0.
Create_user_priv. Determine whether the USER can execute the create user command to CREATE a new MySQL account.
Event_priv. Determine whether a user can create, modify, and delete events. This permission is added to MySQL 5.1.6.
Trigger_priv. Determine whether a user can create or delete a trigger. This permission is added to MySQL 5.1.6.

Restoration of MySQL MyISAM Table Structure

MySQL multi-Table Union query syntax example

Alternative usage of MySQL table alias

MySQL left join query Experience Summary

How to modify the table structure in mysql