mysql. User table permission field description full introduction

The following is true of Mysql User The table permission fields are described in detail , For your reference , If you are right about Mysql User Table permission fields are not well understood , Take a look at , I believe it will enlighten you .

Select_priv： Determine if users can pass through SELECT Command select data .

Insert_priv： Determine if users can pass through INSERT Command insert data .

Update_priv： Determine if users can pass through UPDATE Command to modify existing data .

Delete_priv： Determine if users can pass through DELETE Command to delete existing data .

Create_priv： Determine if users can create new databases and tables .

Drop_priv： Determine if users can delete existing databases and tables .

Reload_priv： Determine if the user can perform a refresh and reload MySQL Specific commands for the various internal caches used , Including logs 、 jurisdiction 、 host 、 Query and table .

Shutdown_priv： Determine if the user can shut down MySQL The server . Provide this permission to root Any user other than the account , We should be very careful .

Process_priv： Determine if users can pass through SHOW PROCESSLIST Command to view other users' processes .

File_priv： Determine if the user can execute SELECT INTO OUTFILE and LOAD DATA INFILE command .

Grant_priv： Determine whether a user can grant his or her own permission to another user . for example , If the user can insert 、 Select and delete foo Information in the database , And awarded GRANT jurisdiction , Then the user can grant any or all of his rights to any other user in the system .

References_priv： It's just a placeholder for some future features ; It doesn't work right now .

Index_priv： Determine whether users can create and delete table indexes .

Alter_priv： Determine if the user can rename and modify the table structure .

Show_db_priv： Determine if users can view the names of all databases on the server , Include databases that users have sufficient access to . Consider disabling this permission for all users , Unless there's something particularly irresistible .

Super_priv： Determine if users can perform some powerful administrative functions , For example, through KILL Command delete user process , Use SET GLOBAL Modify global MySQL Variable , Execute various commands on replication and logging .

Create_tmp_table_priv： Determine if users can create temporary tables .

Lock_tables_priv： Determine if the user can use LOCK TABLES Command block access to table / modify .

Execute_priv： Determine if the user can execute stored procedures . This permission is only available in MySQL 5.0 And later .

Repl_slave_priv： Determines whether users can read binary log files used to maintain the replicated database environment . This user is on the main system , Facilitates communication between hosts and clients .

Repl_client_priv： Determine if the user can determine the location of the replication slave and master servers .

Create_view_priv： Determine if users can create views . This permission is only available in MySQL 5.0 And later . More information about views , See also 34 Chapter .

Show_view_priv： Determine whether the user can view the view or understand how the view performs . This permission is only available in MySQL 5.0 And later . More information about views , See also 34 Chapter .

Create_routine_priv： Determine whether users can change or discard stored procedures and functions . This permission is in MySQL 5.0 Introduced in .

Alter_routine_priv： Determine whether users can modify or delete storage functions and functions . This permission is in MySQL 5.0 Introduced in .

Create_user_priv： Determine if the user can execute CREATE USER command , This command is used to create a new MySQL Account .

Event_priv： Determine if users can create 、 Modify and delete events . This permission is MySQL 5.1.6 Newly added .

Trigger_priv： Determine if the user can create and delete triggers , This permission is MySQL 5.1.6 Newly added .

That's all Mysql User Table authority field description full introduction .

-----------------------------------------------------------------------------------------------------------------

user The initial contents of the table are explained in detail

among ：

HOST—— Is the designated login ip, for instance user=root host=192.168.1.1 , This means that ,root Users can only pass through 192.168.1.1 Client access .

[ ::1 ]—— It's compatibility support ipv6 Of , It means the same as ipv4 Of 127.0.0.1 Same expression localhost.

[ % ] —— It's a wildcard , If host=192.168.1.%, So it means As long as it is ip by host=192.168.1. Prefix clients can connect , that host=% Words mean all ip Have the right to connect .