MySQL composite index follows the principle of leftmost prefix, and the query condition must include the leftmost column of the index before it can hit the index. 1. The index structure is organized in the order of definition, such as (name, age, city) first sorted by name, and then subdivided in sequence; 2. The hit condition includes continuous combinations starting with the leftmost column, such as WHERE name=... or WHERE name=...AND age=...; 3. If the leftmost column is not included, it cannot be hit if only age or city is used; 4. When creating, the high-divided and commonly used query fields should be placed in front of it, and redundancy and excessive indexing should be avoided; 5. Using functions, OR without index support, fuzzy matching at the beginning of % will cause the index to fail.
The Composite Index of MySQL, also known as a joint index, refers to the index created on multiple columns of a table. The rational use of composite indexes can significantly improve query performance, but if you do not understand its principles, it may have a negative effect.

The basic structure of composite index
Composite indexes are organized in the order of columns when defined. For example, if you create an index (name, age, city)
, then the index is sorted by name
first, then sorted by age
when name
is the same, and finally sorted by city
.
For example:

CREATE INDEX idx_name_age_city ON users(name, age, city);
This statement will create a composite index on name
, age
, and city
of the users
table.
This structure determines that when you write query conditions, you should try to start using it from the leftmost column, otherwise the index may not take effect.

How to effectively utilize composite indexes?
The key to using composite indexes is the "leftmost prefix" principle. That is, the query condition must include the column on the leftmost index in order to hit the index.
Several common situations:
-
WHERE name = 'Tom'
? Can hit it -
WHERE name = 'Tom' AND age = 25
? Can hit -
WHERE name = 'Tom' AND age > 20 AND city = 'Beijing'
? Can hit it -
WHERE age = 25 AND city = 'Beijing'
? It will not hit because the leftmost columnname
is not used -
WHERE city = 'Beijing'
? Also won't hit
Therefore, when designing a query statement, try to let the conditions start from the leftmost column of the composite index, so that it is possible to scan the index.
Suggestions for creating composite indexes
Creating a composite index does not just add a few columns together. There are a few practical suggestions:
Highly distinguished column front
For example, compared with gender and age, the age difference is higher and more suitable for putting it in front.Commonly used query fields are preferred
If you often use(user_id, status)
as query conditions, then these two fields are suitable for forming a composite index.Avoid redundant indexing
For example, if you already have(name, age)
index, it will be unnecessary to create a(name)
index separately, because the former can already cover the needs of the latter.Don't over-create indexes
Although indexing speeds up querying, it will also affect insertion and update performance. Especially for tables with more writing and less reading, the more indexes, the greater the burden.
Note: Common scenarios of index failure
Even if you create a composite index, if the query method is wrong, you still cannot hit the index:
- Manipulate fields with functions or expressions, for example:
WHERE YEAR(create_time) = 2023
-
OR
and some conditions are not supported by index - There are fuzzy matches starting with
%
in the query, for example:WHERE name LIKE '%Tom'
These will cause index failure and special attention is required.
Basically that's it. Composite indexing is a good tool, but you have to use the right place and understand its structure and usage rules to truly give full play to your performance advantages.
The above is the detailed content of mysql composite index example. 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

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.

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

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

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.

IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation

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;

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_

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.
