The MySQL indexing mechanism is the core of database optimization, and reasonable use can significantly improve performance. Common types include: 1. The primary key index is unique and non-empty, and it is recommended to use self-increment integer type; 2. The unique index ensures that the column value is unique, suitable for deduplication fields such as usernames; 3. Ordinary index is used to accelerate WHERE conditional query, suitable for fields with low repetition rate; 4. The joint index is based on multiple fields, follows the principle of leftmost matching, and the fields with high distinction degree are placed in front; 5. The full-text index is suitable for large text fuzzy searches, and Chinese word segmentation and delay issues need to be paid attention to.
MySQL's indexing mechanism is one of the core of database performance optimization. If you find that the query is slow and the data volume is stuttering, it is likely that it is because the index is not used well, or the inappropriate index is used.
MySQL supports multiple types of indexes, each of which is different in application scenarios. Understanding their differences and usage methods can help you better improve query efficiency. Let’s start with common index types, and then take a look at how to select and optimize them in actual applications.
Primary Key Index (PRIMARY KEY): Unique and non-empty
The primary key index is a field in a table that uniquely identifies each row record. It has two characteristics:
- Uniqueness: Cannot be repeated
- Non-emptiness: Cannot be NULL
Usually we will use the autoincrement ID as the primary key, such as id INT AUTO_INCREMENT PRIMARY KEY . This approach is simple and efficient, especially when doing association queries.
suggestion:
- Each table should have a primary key
- Try to use integer primary keys, because they are faster
- Do not modify the primary key value frequently, as it may easily cause chain update problems
Unique index (UNIQUE): Ensure that column values ??are unique
Unique indexes are similar to primary keys, and also require that column values ??are unique, but allow multiple NULL values ??(specific behavior depends on database implementation). Suitable for use in fields such as username, mobile phone number, etc. that need to be deduplicated.
For example:
CREATE UNIQUE INDEX idx_username ON users(username);
Notes on use:
- Inserting the duplicate value will cause an error, and it needs to be judged or processed in advance.
- Query speed is slightly slower than normal indexes because you need to check uniqueness
Normal Index (INDEX): The most commonly used acceleration tool
There is no uniqueness limit for ordinary indexes, and they are mainly used to speed up query speed. Applicable to fields that often appear in WHERE conditions, such as order status, user gender, etc.
When to add?
- Fields are often used to filter data
- The data duplication rate is not high (too much repetition may not go through the index)
- When combining queries, you can consider establishing a joint index
For example:
CREATE INDEX idx_status ON orders(status);
This will be faster when querying completed orders:
SELECT * FROM orders WHERE status = 'completed';
Composite Index: Combination punch is more effective
Union indexes are indexes created based on multiple fields and are suitable for multi-conditional queries. For example, we often check orders based on user ID and time range:
CREATE INDEX idx_user_time ON orders(user_id, created_at);
Key points to use:
- The principle of leftmost matching is very important: Only when the leading column is used will the following one take effect.
- The order is very particular: putting fields with high distinction in front of them is better
- Don't add too many fields at will, the index itself also has maintenance costs
For example, this query will hit the above joint index:
SELECT * FROM orders WHERE user_id = 123 AND created_at > '2024-01-01';
But if you only look for created_at, it will not hit.
Full-text index (FULLTEXT): Specialized text search
When you need to fuzzy match large text fields such as article content and product description, ordinary LIKE operations are very inefficient. At this time, you can consider the full text index.
Created as follows:
CREATE FULLTEXT INDEX idx_content ON articles(content);
Then you can use the MATCH AGAINST syntax to query:
SELECT * FROM articles WHERE MATCH(content) AGAINST('database');
Notes:
- Limited support for Chinese, and it needs to be used with word segmentation plug-in
- There is a certain delay, not real-time update
- Not suitable for exact matching, more suitable for natural language search
Basically these commonly used index types. Although there are not many types, there are still many details to pay attention to when using them. Rational use of indexes can not only improve query speed, but also reduce server resource consumption.
The above is the detailed content of Deep Dive into MySQL Indexing Types and Usage. For more information, please follow other related articles on the PHP Chinese website!
Hot AI Tools
Undress AI Tool
Undress images for free
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
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
What is GTID (Global Transaction Identifier) and what are its advantages?
Jun 19, 2025 am 01:03 AM
GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.
What is a typical process for MySQL master failover?
Jun 19, 2025 am 01:06 AM
MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to
How to connect to a MySQL database using the command line?
Jun 19, 2025 am 01:05 AM
The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands
Why do indexes improve MySQL query speed?
Jun 19, 2025 am 01:05 AM
IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation
Why is InnoDB the recommended storage engine now?
Jun 17, 2025 am 09:18 AM
InnoDB is MySQL's default storage engine because it outperforms other engines such as MyISAM in terms of reliability, concurrency performance and crash recovery. 1. It supports transaction processing, follows ACID principles, ensures data integrity, and is suitable for key data scenarios such as financial records or user accounts; 2. It adopts row-level locks instead of table-level locks to improve performance and throughput in high concurrent write environments; 3. It has a crash recovery mechanism and automatic repair function, and supports foreign key constraints to ensure data consistency and reference integrity, and prevent isolated records and data inconsistencies.
What are the transaction isolation levels in MySQL, and which is the default?
Jun 23, 2025 pm 03:05 PM
MySQL's default transaction isolation level is RepeatableRead, which prevents dirty reads and non-repeatable reads through MVCC and gap locks, and avoids phantom reading in most cases; other major levels include read uncommitted (ReadUncommitted), allowing dirty reads but the fastest performance, 1. Read Committed (ReadCommitted) ensures that the submitted data is read but may encounter non-repeatable reads and phantom readings, 2. RepeatableRead default level ensures that multiple reads within the transaction are consistent, 3. Serialization (Serializable) the highest level, prevents other transactions from modifying data through locks, ensuring data integrity but sacrificing performance;
What are the ACID properties of a MySQL transaction?
Jun 20, 2025 am 01:06 AM
MySQL transactions follow ACID characteristics to ensure the reliability and consistency of database transactions. First, atomicity ensures that transactions are executed as an indivisible whole, either all succeed or all fail to roll back. For example, withdrawals and deposits must be completed or not occur at the same time in the transfer operation; second, consistency ensures that transactions transition the database from one valid state to another, and maintains the correct data logic through mechanisms such as constraints and triggers; third, isolation controls the visibility of multiple transactions when concurrent execution, prevents dirty reading, non-repeatable reading and fantasy reading. MySQL supports ReadUncommitted and ReadCommi.
How to add the MySQL bin directory to the system PATH
Jul 01, 2025 am 01:39 AM
To add MySQL's bin directory to the system PATH, it needs to be configured according to the different operating systems. 1. Windows system: Find the bin folder in the MySQL installation directory (the default path is usually C:\ProgramFiles\MySQL\MySQLServerX.X\bin), right-click "This Computer" → "Properties" → "Advanced System Settings" → "Environment Variables", select Path in "System Variables" and edit it, add the MySQLbin path, save it and restart the command prompt and enter mysql--version verification; 2.macOS and Linux systems: Bash users edit ~/.bashrc or ~/.bash_
