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!

InnoDB uses redologs and undologs to ensure data consistency and reliability. 1.redologs record data page modification to ensure crash recovery and transaction persistence. 2.undologs records the original data value and supports transaction rollback and MVCC.

Key metrics for EXPLAIN commands include type, key, rows, and Extra. 1) The type reflects the access type of the query. The higher the value, the higher the efficiency, such as const is better than ALL. 2) The key displays the index used, and NULL indicates no index. 3) rows estimates the number of scanned rows, affecting query performance. 4) Extra provides additional information, such as Usingfilesort prompts that it needs to be optimized.

Usingtemporary indicates that the need to create temporary tables in MySQL queries, which are commonly found in ORDERBY using DISTINCT, GROUPBY, or non-indexed columns. You can avoid the occurrence of indexes and rewrite queries and improve query performance. Specifically, when Usingtemporary appears in EXPLAIN output, it means that MySQL needs to create temporary tables to handle queries. This usually occurs when: 1) deduplication or grouping when using DISTINCT or GROUPBY; 2) sort when ORDERBY contains non-index columns; 3) use complex subquery or join operations. Optimization methods include: 1) ORDERBY and GROUPB

MySQL/InnoDB supports four transaction isolation levels: ReadUncommitted, ReadCommitted, RepeatableRead and Serializable. 1.ReadUncommitted allows reading of uncommitted data, which may cause dirty reading. 2. ReadCommitted avoids dirty reading, but non-repeatable reading may occur. 3.RepeatableRead is the default level, avoiding dirty reading and non-repeatable reading, but phantom reading may occur. 4. Serializable avoids all concurrency problems but reduces concurrency. Choosing the appropriate isolation level requires balancing data consistency and performance requirements.

MySQL is suitable for web applications and content management systems and is popular for its open source, high performance and ease of use. 1) Compared with PostgreSQL, MySQL performs better in simple queries and high concurrent read operations. 2) Compared with Oracle, MySQL is more popular among small and medium-sized enterprises because of its open source and low cost. 3) Compared with Microsoft SQL Server, MySQL is more suitable for cross-platform applications. 4) Unlike MongoDB, MySQL is more suitable for structured data and transaction processing.

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.

The MySQL learning path includes basic knowledge, core concepts, usage examples, and optimization techniques. 1) Understand basic concepts such as tables, rows, columns, and SQL queries. 2) Learn the definition, working principles and advantages of MySQL. 3) Master basic CRUD operations and advanced usage, such as indexes and stored procedures. 4) Familiar with common error debugging and performance optimization suggestions, such as rational use of indexes and optimization queries. Through these steps, you will have a full grasp of the use and optimization of MySQL.

MySQL's real-world applications include basic database design and complex query optimization. 1) Basic usage: used to store and manage user data, such as inserting, querying, updating and deleting user information. 2) Advanced usage: Handle complex business logic, such as order and inventory management of e-commerce platforms. 3) Performance optimization: Improve performance by rationally using indexes, partition tables and query caches.


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

Dreamweaver Mac version
Visual web development tools

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function

SublimeText3 Linux new version
SublimeText3 Linux latest version

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.