What are the permission tables of mysql?
Mysql's permission tables include: 1. User table, used to record account information that is 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 environment of this tutorial: windows7 system, mysql8 version, 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.
user permission table
The user table is the most important permission table in MySQL, used to record account information 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 | |
blob | NO | Support x509 Standard fields | ||
blob | NO | Support x509 standard fields | ||
#char(64) | NO | mysql_native_password | Introducing plugins for password verification when users connect, plugin Create external/proxy user | |
enum('N','Y') | NO | N | Whether the password has expired (N has not expired, y has expired) | |
timestamp | YES | Record the time when the password was last modified | ||
smallint(5) unsigned | YES | Set the password validity time in days | ||
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.
db table
The db table is commonly used and is a very important permission table in the MySQL database. The table stores the user's permissions for a certain database. operating authority. The fields in the table can be roughly divided into two categories, namely user columns and permission columns.
User column
The db table user column has 3 fields, namely Host, User, and Db, which identify a user connecting to a database from a certain host. The combination of these three 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 |
Permission columns
The permission columns in the db table are roughly the same as those in the user table, except that the Permissions are for all databases, while the permissions in the db table are only for the specified database. If you want the user to have operation permissions only for a certain database, you can first set the corresponding permissions in the user table to N, and then set the operation permissions for the corresponding database in the db table.tables_priv table and columns_priv table
The tables_priv table is used to set permissions on a single table, and the columns_priv table is used to set permissions on a single data column. set up. The tables_priv table structure is as shown in the following table:Field type | Is it empty | Default value | Description | |
---|---|---|---|---|
char(60) | NO | None | Host | |
char(64) | NO | None | Database name | |
char(32) | NO | None | Username | |
char(64) | NO | None | Table name | |
char(93) | NO | None | User who modified this record | |
timestamp | NO | CURRENT_TIMESTAMP | The time to modify the record | |
set( 'Select','Insert','Update','Delete',' | Create','Drop','Grant','References', 'Index','Alter','Create View' ,'Show view','Trigger') | NONone | indicates the operation permissions on the table, including Select, Insert, Update, Delete, Create, Drop, Grant, References, Index and Alter, etc. | |
set('Select','Insert','Update','References') | NO | None | Indicates the operation permissions on the columns in the table, including Select, Insert, Update and References |
Field name | Field type | Is it empty | Default value | Description |
---|---|---|---|---|
char(60) | NO | None | Host | |
char(64) | NO | None | Database name | |
char(32) | NO | None | Username | |
char(64) | NO | None | Table name | |
char(64) | NO | None | Data column name, used to specify which data columns have operation permissions | |
timestamp | NO | CURRENT_TIMESTAMP | Modify the time of this record | |
set('Select','Insert','Update','References') | NO | None | means yes Operation permissions for columns in the table, including Select, Insert, Update and References |
##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:
Whether it is empty | Default value | Description | Host | |
---|---|---|---|---|
NO | None | Host Name | Db | |
NO | None | Database name | User | |
NO | None | Username | Routine_name | |
NO | None | Represents the name of a stored procedure or function | Routine_type | |
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. | |
NO | None | User who inserted or modified this record | Proc_priv | |
NO | None | indicates the permissions you have, including Execute, Alter Routine, and Grant. | Timestamp | |
NO | CURRENT_TIMESTAMP | indicates the record update time |
The above is the detailed content of What are the permission tables of mysql?. 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

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

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











The main role of MySQL in web applications is to store and manage data. 1.MySQL efficiently processes user information, product catalogs, transaction records and other data. 2. Through SQL query, developers can extract information from the database to generate dynamic content. 3.MySQL works based on the client-server model to ensure acceptable query speed.

Laravel is a PHP framework for easy building of web applications. It provides a range of powerful features including: Installation: Install the Laravel CLI globally with Composer and create applications in the project directory. Routing: Define the relationship between the URL and the handler in routes/web.php. View: Create a view in resources/views to render the application's interface. Database Integration: Provides out-of-the-box integration with databases such as MySQL and uses migration to create and modify tables. Model and Controller: The model represents the database entity and the controller processes HTTP requests.

MySQL and phpMyAdmin are powerful database management tools. 1) MySQL is used to create databases and tables, and to execute DML and SQL queries. 2) phpMyAdmin provides an intuitive interface for database management, table structure management, data operations and user permission management.

Compared with other programming languages, MySQL is mainly used to store and manage data, while other languages such as Python, Java, and C are used for logical processing and application development. MySQL is known for its high performance, scalability and cross-platform support, suitable for data management needs, while other languages have advantages in their respective fields such as data analytics, enterprise applications, and system programming.

I encountered a tricky problem when developing a small application: the need to quickly integrate a lightweight database operation library. After trying multiple libraries, I found that they either have too much functionality or are not very compatible. Eventually, I found minii/db, a simplified version based on Yii2 that solved my problem perfectly.

Article summary: This article provides detailed step-by-step instructions to guide readers on how to easily install the Laravel framework. Laravel is a powerful PHP framework that speeds up the development process of web applications. This tutorial covers the installation process from system requirements to configuring databases and setting up routing. By following these steps, readers can quickly and efficiently lay a solid foundation for their Laravel project.

The basic operations of MySQL include creating databases, tables, and using SQL to perform CRUD operations on data. 1. Create a database: CREATEDATABASEmy_first_db; 2. Create a table: CREATETABLEbooks(idINTAUTO_INCREMENTPRIMARYKEY, titleVARCHAR(100)NOTNULL, authorVARCHAR(100)NOTNULL, published_yearINT); 3. Insert data: INSERTINTObooks(title, author, published_year)VA

When developing an e-commerce website using Thelia, I encountered a tricky problem: MySQL mode is not set properly, causing some features to not function properly. After some exploration, I found a module called TheliaMySQLModesChecker, which is able to automatically fix the MySQL pattern required by Thelia, completely solving my troubles.
