- 13.2.8 Subquery Syntax
- 13.2.8.1 The Subquery as Scalar Operand
- 13.2.8.2 Comparisons Using Subqueries
- 13.2.8.3 Subqueries with ANY, IN, and SOME
- 13.2.8.4 Subqueries with ALL
- 13.2.8.5 Row Subqueries
- 13.2.8.6 EXISTS and NOT EXISTS
- 13.2.8.7 Correlated Subqueries
- 13.2.8.8 Subqueries in the FROM clause
- 13.2.8.9 Subquery Errors
- 13.2.8.10 Optimizing Subqueries
- 13.2.8.11 Rewriting Subqueries as Joins for Earlier MySQL Versions
In previous versions of MySQL (prior to MySQL 4.1), only
nested queries of the form INSERT ... SELECT
... and REPLACE ... SELECT ...
were supported. Although this is not the case in MySQL
5.1, it is still true that there are sometimes
other ways to test membership in a set of values. It is also
true that on some occasions, it is not only possible to
rewrite a query without a subquery, but it can be more
efficient to make use of some of these techniques rather than
to use subqueries. One of these is the IN()
construct:
For example, this query:
SELECT * FROM t1 WHERE id IN (SELECT id FROM t2);
Can be rewritten as:
SELECT DISTINCT t1.* FROM t1, t2 WHERE t1.id=t2.id;
The queries:
SELECT * FROM t1 WHERE id NOT IN (SELECT id FROM t2); SELECT * FROM t1 WHERE NOT EXISTS (SELECT id FROM t2 WHERE t1.id=t2.id);
Can be rewritten using IN():
SELECT table1.* FROM table1 LEFT JOIN table2 ON table1.id=table2.id WHERE table2.id IS NULL;
A LEFT [OUTER] JOIN can be faster than an
equivalent subquery because the server might be able to
optimize it better — a fact that is not specific to
MySQL Server alone. Prior to SQL-92, outer joins did not
exist, so subqueries were the only way to do certain things.
Today, MySQL Server and many other modern database systems
offer a wide range of outer join types.
MySQL Server supports multiple-table DELETE
statements that can be used to efficiently delete rows based
on information from one table or even from many tables at the
same time. Multiple-table UPDATE statements
are also supported. See Section 13.2.1, “DELETE Syntax”, and
Section 13.2.10, “UPDATE Syntax”.
User Comments
Here is a rough description of one more method to do something equivalent to a subquery in a DELETE for older versions of MySQL that do not support it. It only works for the case where there is a unique key on the table. It requires making a temporary table and a temporary column on the table from which you wish to delete. However it's all done in a sequence of SQL commands which is a little cleaner than the other methods.
Let's say the table from which you want to delete is "origtable". First create a temporary table with the same structure as origtable (though without autoincrement columns), let's call it "temptable". Then fill it with the rows of origtable that you wish to delete, for example:
INSERT INTO temptable SELECT ... FROM origtable WHERE ...
It's important that all results from the SELECT statement should have unique keys that are present in origtable, in other words don't do something weird here like taking the cosine of the primary key. Next create a temporary new column on origtable to designate which rows you intend to delete, and default this to 1:
ALTER TABLE origtable ADD `tempdeleteflag` int(12) NOT NULL default 1;
Next set tempdeleteflag to 0 for the rows that are present in temptable using REPLACE:
REPLACE origtable SELECT id, col1, col2, ..., colN, 0 FROM temptable;
Now tempdeleteflag should be set to 0 for rows you intended to keep or 1 for rows you inteded to delete, so:
DELETE FROM origtable WHERE tempdeleteflag = 1;
Finally clean up the temporary column:
ALTER TABLE origtable DROP tempdeleteflag;
If you created temptable using TEMPORARY it will go away when your session ends, otherwise drop it now.
As an alternative, you can do the logic the other way here:
default tempdeleteflag to 0, select rows you wish to delete into temptable, then set tempdeleteflag to 1 on rows common to the two tables.
In reference to the first user comment on this page, I have 2 comments:
1) GREAT CONCEPT - I use it a lot now!
2) You actually made a typo, and if done exactly as you describe you will delete all the rows you wanted to keep, and keep those you wanted to delete!.
You say to create a "temptable" and fill it with the rows you wish to delete... this should say "fill it with the rows you wish to KEEP", alternatively the following SQL DELETE statement should be inverted so that you delete those "where tempdeleteflag = 0";
Why? Well, you are defaulting the origtable to have a value of 1 in the tempdeleteflag column, and then setting it to 0 for those that you want to DELETE. (0 means delete) obviously then the DELETE statement should delete those that are 0. Alternatively, if you set it to 0 for those that you want to KEEP (0 means keep, then 1 means DELETE) then you DELETE those that are set to 1. Be very careful to get it right.
About the above comments, if one can
INSERT INTO temptable SELECT ... FROM origtable WHERE ...
to choose exactly what to DELETE, why not simply
DELETE FROM origtable WHERE <same where clause as above>
and be done with it?
About the last comment, presumably the select involves a join which a straight delete could not.
A final method is to use a left join to remove those rows you dont want from the results set and insert that results set into a new table and swap that table witht the table you wanted to delete from...
I hate this method so much I am hear reading how to do this....
DELETE FROM
WHERE
ROW(SUNID1,SUNID2) IN (
SELECT
SUNID1,SUNID2
FROM
toExcludeFromInterfaceBreakdown
);
Yay for subselects!
Add your own comment.