Description\n-----------\n\nsubqueries-and-all.md\n\nCompare a value against all results from a subquery. The ALL operator returns TRUE if the comparison holds for every row returned by the subquery.\n\nsubqueries-and-any.md\n\nCompare a value against any result from a subquery. The ANY (or SOME) operator returns TRUE if the comparison holds for at least one row. IN can be used for =ANY.\n\nsubqueries-and-exists.md\n\nTest for the existence of rows. The EXISTS operator returns TRUE if the subquery returns at least one row, often used for correlated subqueries.\n\nsubqueries-and-joins.md\n\nUnderstand when to use subqueries versus joins. This guide explains performance implications and how to rewrite subqueries as joins for efficiency.\n\nsubqueries-in-a-from-clause-derived-tables.md\n\nUse a subquery as a temporary table. Derived tables allow you to select from the result set of another query within the FROM clause.\n\nsubqueries-row-subqueries.md\n\nRetrieve a single row of multiple values. A row subquery returns a tuple that can be compared against a row constructor in the outer query.\n\nsubqueries-scalar-subqueries.md\n\nReturn a single value. A scalar subquery produces a one-row, one-column result that can be used anywhere a constant or expression is valid.\n\nsubquery-limitations.md\n\nReview restrictions on subquery usage. This page details unsupported operations, such as modifying a table while selecting from it in a subquery.\n\nURL: https://mariadb.com/docs/server/reference/sql-statements/data-manipulation/selecting-data/joins-subqueries/subqueries/README