What are the permission tables of mysql database?
MySQL database permission tables include: 1. user table, used to record account information allowed to connect to the server. All permissions enabled in this table are global level and apply to all databases; 2. db table , stores the user's operating permissions for a certain database; 3. tables_priv table, used to set permissions for a single table; 4. columns_priv table, used to set permissions for a single data column; 5. procs_priv table, used for storage Procedures and stored functions set permissions.
The operating system of this tutorial: Windows 10 system, mysql version 8.0, Dell G3 computer.
In the MySQL database, the permission tables include the user table, db table, tables_priv table, columns_priv table and procs_priv table.
1. User permission table
The user table is the most important permission table in MySQL, used to record account information that is allowed to connect to the server. It should be noted that all permissions enabled in the user table are global and apply to all databases.
The fields in the user table can be roughly divided into 4 categories, namely user columns, permission columns, security columns and resource control columns.
User column
The user column stores the information that users need to enter when connecting to the MySQL database. It should be noted that MySQL 5.7 version no longer uses Password as the password field, but changed it to authentication_string.
Permission column
The fields in the permission column determine the user's permissions and are used to describe the operations allowed on data and databases in the global scope.
Permissions are roughly divided into two categories, namely advanced management permissions and ordinary permissions:
Advanced management permissions mainly manage the database, such as the permission to close services, Super permissions and loading users, etc.;
Normal permissions mainly operate the database, such as query permissions, modification permissions, etc.
The permission columns of the user table include Select_priv, Insert_ priv and other fields ending with priv. The data type of these field values is ENUM. The only possible values are Y and N: Y represents the user There are corresponding permissions, N means that the user does not have the corresponding permissions. For security reasons, the default value for these fields is N.
If you want to modify the permissions, you can use the GRANT statement to grant some permissions to the user, or you can set the permissions by updating the user table with the UPDATE statement.
Security column
The security column is mainly used to determine whether the user can log in successfully. The security column in the user table is as shown in the following table:
Field name | Field type | Is it empty | Default value | Description |
---|---|---|---|---|
ssl_type | enum('','ANY','X509','SPECIFIED') | NO | Support ssl standard encryption security field | |
ssl_cipher | blob | NO | Support ssl standard encryption security field | |
x509_issuer | blob | NO | Support x509 standard fields | |
x509_subject | blob | NO | Support x509 standard fields | |
plugin | char(64) | NO | mysql_native_password | Introducing plugins for password verification when users connect, plugin creates external/proxy users |
password_expired | enum('N','Y') | NO | N | Whether the password has expired (N has not expired, y has expired) |
password_last_changed | timestamp | YES | ||
smallint (5) unsigned | YES | |||
enum('N','Y') | NO | N | Whether the user is locked (Y is locked, N is not locked) |
Field name | Field type | Whether it is empty | Default value | Description |
---|---|---|---|---|
max_questions | int(11) unsigned | NO | 0 | Specifies the number of query operations allowed per hour |
max_updates | int(11) unsigned | NO | 0 | Specifies the number of update operations allowed per hour |
max_connections | int(11) unsigned | NO | 0 | Specifies the number of connection operations allowed per hour |
max_user_connections | int(11) unsigned | NO | 0 | Specifies the number of connections allowed to be established simultaneously |
The default value of the above fields is 0, indicating no limit. If the number of user queries or connections exceeds the resource control limit within an hour, the user will be locked and cannot perform corresponding operations here until the next hour. The values of these fields can be updated using the GRANT statement.
2. db table
The db table is commonly used and is a very important permissions table in the MySQL database. The table stores the user's operating permissions for a certain database. The fields in the table can be roughly divided into two categories, namely user columns and permission columns.
User column
db table user column has 3 fields, namely Host, User, and Db, which identify the operation permission of a user to connect to a certain database from a certain host. These 3 fields The combination of fields constitutes the primary key of the db table.
The user list of the db table is as shown in the following table:
Field name | Field type | Is it empty? | Default value | Description |
---|---|---|---|---|
Host | char(60) | NO | None | Host name |
char(64) | NO | None | Database name | |
char(32) | NO | None | User name |
Field name | Field type | Whether it is empty | Default value | Description |
---|---|---|---|---|
Host | char(60) | NO | None | Host |
Db | char(64) | NO | None | Database name |
User | char(32) | NO | None | Username |
Table_name | char (64) | NO | None | Table name |
Grantor | char(93) | NO | None | User who modified this record |
Timestamp | timestamp | NO | CURRENT_TIMESTAMP | The time to modify the record |
Table_priv | set('Select','Insert','Update' ,'Delete',' Create','Drop','Grant','References', 'Index','Alter','Create View','Show view','Trigger') |
NO | None | Indicates the operation permissions on the table, including Select, Insert, Update, Delete, Create, Drop, Grant, References, Index and Alter, etc. |
Column_priv | set('Select','Insert','Update','References') | NO | None | Indicates the operation permissions on the columns in the table, including Select, Insert, Update and References |
4. columns_priv table
columns_priv table is used to set permissions on a single data column, columns_priv The table structure is as shown in the following table:
Field name | Field type | Is it empty | Default value | Description |
---|---|---|---|---|
Host | char(60) | NO | No | Host |
Db | char(64) | NO | None | Database name |
User | char(32) | NO | None | Username |
Table_name | char(64) | NO | None | Table name |
Column_name | char(64) | NO | None | Data column name, used to specify which data columns have operation permissions |
Timestamp | timestamp | NO | CURRENT_TIMESTAMP | Modify the time of this record |
Column_priv | set('Select','Insert','Update','References') | NO | None | Indicates the column in the table Operation permissions, including Select, Insert, Update and References |
5. procs_priv table
The procs_priv table can set permissions on stored procedures and stored functions. The table structure of procs_priv is as shown in the table:
Field name | Field type | Whether it is empty | Default value | Description |
---|---|---|---|---|
Host | char(60) | NO | None | Host name |
Db | char(64) | NO | None | Database name |
User | char(32) | NO | None | Username |
Routine_name | char(64) | NO | None | Indicates the name of the stored procedure or function |
Routine_type | enum('FUNCTION','PROCEDURE') | NO | None | indicates the type of stored procedure or function. The Routine_type field has two values, namely FUNCTION and PROCEDURE . FUNCTION indicates that this is a function; PROCEDURE indicates that this is a stored procedure. |
Grantor | char(93) | NO | None | User who inserted or modified this record |
Proc_priv | set('Execute','Alter Routine','Grant') | NO | None | indicates the permissions you have, including Execute, Alter Routine, and Grant. |
Timestamp | timestamp | NO | CURRENT_TIMESTAMP | indicates the record update time |
The above is the detailed content of What are the permission tables of mysql database?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



MySQL is suitable for beginners because it is simple to install, powerful and easy to manage data. 1. Simple installation and configuration, suitable for a variety of operating systems. 2. Support basic operations such as creating databases and tables, inserting, querying, updating and deleting data. 3. Provide advanced functions such as JOIN operations and subqueries. 4. Performance can be improved through indexing, query optimization and table partitioning. 5. Support backup, recovery and security measures to ensure data security and consistency.

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

You can open phpMyAdmin through the following steps: 1. Log in to the website control panel; 2. Find and click the phpMyAdmin icon; 3. Enter MySQL credentials; 4. Click "Login".

Create a database using Navicat Premium: Connect to the database server and enter the connection parameters. Right-click on the server and select Create Database. Enter the name of the new database and the specified character set and collation. Connect to the new database and create the table in the Object Browser. Right-click on the table and select Insert Data to insert the data.

MySQL and SQL are essential skills for developers. 1.MySQL is an open source relational database management system, and SQL is the standard language used to manage and operate databases. 2.MySQL supports multiple storage engines through efficient data storage and retrieval functions, and SQL completes complex data operations through simple statements. 3. Examples of usage include basic queries and advanced queries, such as filtering and sorting by condition. 4. Common errors include syntax errors and performance issues, which can be optimized by checking SQL statements and using EXPLAIN commands. 5. Performance optimization techniques include using indexes, avoiding full table scanning, optimizing JOIN operations and improving code readability.

You can create a new MySQL connection in Navicat by following the steps: Open the application and select New Connection (Ctrl N). Select "MySQL" as the connection type. Enter the hostname/IP address, port, username, and password. (Optional) Configure advanced options. Save the connection and enter the connection name.

Recovering deleted rows directly from the database is usually impossible unless there is a backup or transaction rollback mechanism. Key point: Transaction rollback: Execute ROLLBACK before the transaction is committed to recover data. Backup: Regular backup of the database can be used to quickly restore data. Database snapshot: You can create a read-only copy of the database and restore the data after the data is deleted accidentally. Use DELETE statement with caution: Check the conditions carefully to avoid accidentally deleting data. Use the WHERE clause: explicitly specify the data to be deleted. Use the test environment: Test before performing a DELETE operation.

Redis uses a single threaded architecture to provide high performance, simplicity, and consistency. It utilizes I/O multiplexing, event loops, non-blocking I/O, and shared memory to improve concurrency, but with limitations of concurrency limitations, single point of failure, and unsuitable for write-intensive workloads.