Subquery
MySQL 4.1 introduced support for subqueries, so to use the SQL described in this chapter, you must use MySQL 4.1 or higher.
SELECT statement is a SQL query. All SELECT statements we have seen so far have been simple queries, i.e., single statements that retrieve data from a single database table.
Query (query) Any SQL statement is a query. However, this term generally refers to the SELECT statement.
SQL also allows the creation of subqueries (subquery), that is, queries nested in other queries. Why do we do this? The best way to understand this concept is to examine a few examples.
Filtering using subqueries
The database tables used in all chapters of this book are relational tables (for a description of each table and relationship, please refer to Appendix B ). Orders are stored in two tables. The orders table stores one row for each order that contains the order number, customer ID, and order date. Items for each order are stored in the related orderitems table. The orders table does not store customer information. It only stores the customer's ID. The actual customer information is stored in the customers table. Now, if you need to list all customers who ordered item TNT2, how should you retrieve it? Specific steps are listed below.
(1) Retrieve the numbers of all orders containing item TNT2.
(2) Retrieve the IDs of all customers with the order number listed in the previous step.
(3) Retrieve the customer information of all customer IDs returned in the previous step.
Each of the above steps can be executed as a separate query. The results returned by one SELECT statement can be used in the WHERE clause of another SELECT statement.
You can also use subqueries to combine 3 queries into one statement.
The meaning of the first SELECT statement is clear, for all order items with prod_id TNT2, it retrieves their order_num column. Output lists two orders that contain this item:
Input:
select order_num from orderitems where prod_id = 'TNT2';
Output:
Next, query with order 20005 and customer ID 20007. Using the IN clause, write the following SELECT statement:
Input:
select cust_id from orders where order_num in (20005,20007);
Output:
Now, put the first query (the one that returns the order number) becomes a subquery combining the two queries. Please look at the following SELECT statement:
Input:
select cust_id from orders where order_num in (select order_num from orderitems where prod_id = 'TNT2');
Output:
Analysis: In the SELECT statement, the subquery is always Work from the inside out. When processing the above SELECT statement, MySQL actually performs two operations.
First, it executes the following query:
select order_num from orderitems where prod_id = 'TNT2';
This query returns two order numbers: 20005 and 20007. These two values are then passed to the WHERE clause of the outer query in the comma-separated format required by the IN operator. The outer query becomes:
select cust_id from orders where order_num in (20005,20007);
As you can see, the output is correct and the same as the value returned by the previous hard-coded WHERE clause.
Formatted SQL SELECT statements that contain subqueries can be difficult to read and debug, especially if they are complex. Breaking the subquery into multiple lines and indenting it appropriately as shown above can greatly simplify the use of subqueries.
Now we have the IDs of all customers who ordered item TNT2. The next step is to retrieve the customer information for these customer IDs. The SQL statement to retrieve two columns is:
Input:
select cust_name,cust_contact from customers where cust_id in (10001,10004);
You can convert the WHERE clause into a subquery instead of hardcoding these customer IDs:
Input:
select cust_name,cust_contact from customers where cust_id in(select cust_id from orders where order_num in(select order_num from orderitems where prod_id = 'TNT2'));
Output:
Analysis: In order to execute the above SELECT statement, MySQL must actually execute 3 SELECT statements. The innermost subquery returns a list of order numbers that is used in the WHERE clause of its outer subquery. The outer subquery returns the list of customer IDs used in the WHERE clause of the outermost query. The outermost query does return the required data.
It can be seen that using subqueries in the WHERE clause can write powerful and flexible SQL statements. There is no limit to the number of nested subqueries, but in actual use due to performance limitations, too many subqueries cannot be nested.
Columns must match When using a subquery in a WHERE clause (as shown here), you should ensure that the SELECT statement has the same number of columns as in the WHERE clause. Typically, a subquery will return and match a single column, but multiple columns can be used if needed.
Although subqueries are generally used in conjunction with the IN operator, they can also be used to test equality ( = ), not equal ( ), etc.
Subquery and Performance The code given here works and gets the desired results. However, using subqueries is not always the most efficient way to perform this type of data retrieval. For more discussion, see Chapter 15, where this example is given again.
[Related recommendations]
mysql creates calculated fields and uses subqueries
#What are joins and relational tables in mysql?
Why use joins and how to create joins
-
The importance of WHERE clause in MySQL and how to join multiple tables
The above is the detailed content of What is a mysql subquery? How to filter using subqueries?. For more information, please follow other related articles on the PHP Chinese website!

Stored procedures are precompiled SQL statements in MySQL for improving performance and simplifying complex operations. 1. Improve performance: After the first compilation, subsequent calls do not need to be recompiled. 2. Improve security: Restrict data table access through permission control. 3. Simplify complex operations: combine multiple SQL statements to simplify application layer logic.

The working principle of MySQL query cache is to store the results of SELECT query, and when the same query is executed again, the cached results are directly returned. 1) Query cache improves database reading performance and finds cached results through hash values. 2) Simple configuration, set query_cache_type and query_cache_size in MySQL configuration file. 3) Use the SQL_NO_CACHE keyword to disable the cache of specific queries. 4) In high-frequency update environments, query cache may cause performance bottlenecks and needs to be optimized for use through monitoring and adjustment of parameters.

The reasons why MySQL is widely used in various projects include: 1. High performance and scalability, supporting multiple storage engines; 2. Easy to use and maintain, simple configuration and rich tools; 3. Rich ecosystem, attracting a large number of community and third-party tool support; 4. Cross-platform support, suitable for multiple operating systems.

The steps for upgrading MySQL database include: 1. Backup the database, 2. Stop the current MySQL service, 3. Install the new version of MySQL, 4. Start the new version of MySQL service, 5. Recover the database. Compatibility issues are required during the upgrade process, and advanced tools such as PerconaToolkit can be used for testing and optimization.

MySQL backup policies include logical backup, physical backup, incremental backup, replication-based backup, and cloud backup. 1. Logical backup uses mysqldump to export database structure and data, which is suitable for small databases and version migrations. 2. Physical backups are fast and comprehensive by copying data files, but require database consistency. 3. Incremental backup uses binary logging to record changes, which is suitable for large databases. 4. Replication-based backup reduces the impact on the production system by backing up from the server. 5. Cloud backups such as AmazonRDS provide automation solutions, but costs and control need to be considered. When selecting a policy, database size, downtime tolerance, recovery time, and recovery point goals should be considered.

MySQLclusteringenhancesdatabaserobustnessandscalabilitybydistributingdataacrossmultiplenodes.ItusestheNDBenginefordatareplicationandfaulttolerance,ensuringhighavailability.Setupinvolvesconfiguringmanagement,data,andSQLnodes,withcarefulmonitoringandpe

Optimizing database schema design in MySQL can improve performance through the following steps: 1. Index optimization: Create indexes on common query columns, balancing the overhead of query and inserting updates. 2. Table structure optimization: Reduce data redundancy through normalization or anti-normalization and improve access efficiency. 3. Data type selection: Use appropriate data types, such as INT instead of VARCHAR, to reduce storage space. 4. Partitioning and sub-table: For large data volumes, use partitioning and sub-table to disperse data to improve query and maintenance efficiency.

TooptimizeMySQLperformance,followthesesteps:1)Implementproperindexingtospeedupqueries,2)UseEXPLAINtoanalyzeandoptimizequeryperformance,3)Adjustserverconfigurationsettingslikeinnodb_buffer_pool_sizeandmax_connections,4)Usepartitioningforlargetablestoi


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 Mac version
God-level code editing software (SublimeText3)

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.

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.
