MySQL avoids index columns using OR conditions
#I have suffered this loss many times. In the sql code before development, many queries with or as the where condition were even updated. Here are examples to illustrate the disadvantages of using or and how to improve it.
select f_crm_id from d_dbname1.t_tbname1 where f_xxx_id = 926067 and (f_mobile ='1234567891' or f_phone ='1234567891' ) limit 1
It is easy to see from the query statement that both fields f_mobile and f_phone may store phone numbers. The general idea is to use or to solve it with a sql, but a large amount of table data is simply a disaster:
t_tbanme1 has the indexes idx_id_mobile(f_xxx_id,f_mobile), idx_phone(f_phone), idx_id_email(f_id,f_email), but the explain result uses the idx_id_email index. Sometimes I am lucky. You may choose idx_id_mobile f_xxx_id
because for each query of mysql, you can only select one index on each table. If the idx_id_mobile index is used and there happens to be one piece of data because there is limit 1, then congratulations on getting the result quickly; but if there is no data for f_mobile, then the f_phone field can only be searched one by one under the f_id condition, scanning 120,000 rows. or is different from and. Some developers even think that adding (f_xxx_id, f_mobile, f_phone) would be perfect. I’m going to vomit blood~
So optimizing sql is very simple (Note that there must be corresponding indexes on f_mobile and f_phone), Method 1:
(select f_crm_id from d_dbname1.t_tbname1 where f_xxx_id = 926067 and f_mobile ='1234567891' limit 1 ) UNION ALL (select f_crm_id from d_dbname1.t_tbname1 where f_xxx_id = 926067 and f_phone ='1234567891' limit 1 )
Two independent SQLs can use the index, and each query has its own limit. If both result sets are returned, just pick one.
There is another optimization method. If this kind of query is particularly frequent (and there is no cache), change it to a separate sql execution. For example, most of the number values are on f_mobile, then execute sql1 first, and there will be results. Then end, judge that there is no result and then execute sql2, which can reduce the database query speed and allow the code to handle more things. Method 2 Pseudo code:
sql1 = select f_crm_id from d_dbname1.t_tbname1 where f_xxx_id = 926067 and f_mobile ='1234567891' limit 1; sq1.execute(); if no result sql1: sql1 = select f_crm_id from d_dbname1.t_tbname1 where f_xxx_id = 926067 and f_phone ='1234567891' limit 1; sql1.execute();
A more complex scenario is the end It is as simple as returning a record, limit 2:
select a.f_crm_id from d_dbname1.t_tbname1 as a where (a.f_create_time > from_unixtime('1464397527') or a.f_modify_time > from_unixtime('1464397527') ) limit 0,200
In this case, methods one and two need to be modified, because both f_create_time and f_modify_time may meet the judgment conditions, so duplicate data will be returned.
Method 1 needs to be modified:
(select a.f_crm_id from d_dbname1.t_tbname1 as a where a.f_create_time > from_unixtime('1464397527') limit 0,200 ) UNION ALL (select a.f_crm_id from d_dbname1.t_tbname1 as a where a.f_modify_time > from_unixtime('1464397527')and a.f_create_time <= from_unixtime('1464397527') limit 0,200)
Some people say that changing UNION ALL to UNION will eliminate the duplication, right? If queries are frequent or the limit is relatively large, the database will still be under pressure, so trade off is required.
This situation is more suitable for method two, including situations where order by limit may be required. Transform the pseudocode:
sql1 = (select a.f_crm_id from d_dbname1.t_tbname1 as a where a.f_create_time > from_unixtime('1464397527') limit 0,200 ); sql1.execute(); sql1_count = sql1.result.count if sql1_count < 200 : sql2 = (select a.f_crm_id from d_dbname1.t_tbname1 as a where a.f_modify_time > from_unixtime('1464397527') and a.f_create_time <= from_unixtime('1464397527') limit 0, (200 - sql1_count) ); sql2.execute(); final_result = paste(sql1,sql2);
or conditions are difficult to optimize on the database. The logic can be optimized in the code so as not to bring down the database. It is only considered when no index is needed under the or condition (and the amount of data to be compared is small).
The same field or can be changed to in, such as f_id=1 or f_id=100 -> f_id in (1,100). For efficiency issues, see the article The efficiency issues of or and in in mysql.
The above optimization scenarios are all storage engines in the case of InnoDB. They are different in MyISAM. See mysql or conditions where you can use indexes to avoid the full table.
The above is the content of MySQL to avoid using OR conditions in index columns. For more related content, please pay attention to the PHP Chinese website (www.php.cn)!

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

MySQL is an open source relational database management system, mainly used to store and retrieve data quickly and reliably. Its working principle includes client requests, query resolution, execution of queries and return results. Examples of usage include creating tables, inserting and querying data, and advanced features such as JOIN operations. Common errors involve SQL syntax, data types, and permissions, and optimization suggestions include the use of indexes, optimized queries, and partitioning of tables.

MySQL's position in databases and programming is very important. It is an open source relational database management system that is widely used in various application scenarios. 1) MySQL provides efficient data storage, organization and retrieval functions, supporting Web, mobile and enterprise-level systems. 2) It uses a client-server architecture, supports multiple storage engines and index optimization. 3) Basic usages include creating tables and inserting data, and advanced usages involve multi-table JOINs and complex queries. 4) Frequently asked questions such as SQL syntax errors and performance issues can be debugged through the EXPLAIN command and slow query log. 5) Performance optimization methods include rational use of indexes, optimized query and use of caches. Best practices include using transactions and PreparedStatemen

MySQL is chosen for its performance, reliability, ease of use, and community support. 1.MySQL provides efficient data storage and retrieval functions, supporting multiple data types and advanced query operations. 2. Adopt client-server architecture and multiple storage engines to support transaction and query optimization. 3. Easy to use, supports a variety of operating systems and programming languages. 4. Have strong community support and provide rich resources and solutions.

Apache connects to a database requires the following steps: Install the database driver. Configure the web.xml file to create a connection pool. Create a JDBC data source and specify the connection settings. Use the JDBC API to access the database from Java code, including getting connections, creating statements, binding parameters, executing queries or updates, and processing results.

The process of starting MySQL in Docker consists of the following steps: Pull the MySQL image to create and start the container, set the root user password, and map the port verification connection Create the database and the user grants all permissions to the database

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.

The key to installing MySQL elegantly is to add the official MySQL repository. The specific steps are as follows: Download the MySQL official GPG key to prevent phishing attacks. Add MySQL repository file: rpm -Uvh https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm Update yum repository cache: yum update installation MySQL: yum install mysql-server startup MySQL service: systemctl start mysqld set up booting
