F855, “Nested ORDER BY in query expression”


BigQueryDb2 (LUW)DuckDBH2MariaDBMySQLOracle DBPostgreSQLSQL ServerSQLite200820102012201420162018202020222024⊘ 3.5.7 - 3.53.0⊘ 2008R2 - 2025⚠ 8.3 - 18a✓ 12cR1 - 23.26.1✓ 5.7 - 9.7.0⊘ 5.0 - 5.6✓ 10.1 - 12.2.2⊘ 5.1 - 10.0.10⚠ 1.4.191 - 2.4.240a✓ 1.0.0 - 1.5.0✓ 9.7 - 12.1.4✓ 2.0+
  1. Some variants

This optional SQL feature covers the order by clause applied to a single leg of an union, intersect or except:

(SELECT *
   FROM (VALUES (1), (2)) t(c)
  ORDER BY c
  FETCH FIRST 1 ROW ONLY
)
UNION ALL
SELECT *
 FROM (VALUES (3)) t(c)
-- ORDER BY here applies to the result of the UNION

The first leg of the union uses an order by clause. Note the such legs need to be put into parenthesis so that the scoping of the order by clause is unambiguous. Adding an order by clause to the last leg of union, intersect or except without parenthesis means to sort the total result.

Variants

This feature allows the following order by keys types: ⓵ references to selected columns by name; ⓶ references to columns produced in the from clause if the query is simple0 and ⓷ expressions that contain at least one such column reference.1 Note that positional referencing by an unsigned integer value ⓸ is not standard SQL anymore. While the standard even allows nested order by clause in absences of offset and fetch first, some systems do not allow this pointless clause ⓹.

BigQuery 2026-05-12Db2 (LUW) 12.1.4DuckDB 1.5.0H2 2.4.240abMariaDB 12.2.2cMySQL 9.7.0cOracle DB 23.26.1dPostgreSQL 18aSQL Server 2025dSQLite 3.53.0dselected column ⓵non-selected column ⓶expressions ⓷positional reference ⓸without fetch first, … ⓹
  1. Expressions cannot contain selected names:
    select c AS x FROM (VALUES (1), (2)) t(c) ORDER BY x
  2. Also via bind parameter: order by ? • Negative parameters (but not literals) reverse the direction
  3. Also via bind parameter: order by ?
  4. Reasonable; ignored in other charts

Normative references

F855, “Nested ORDER BY in query expression” is an optional feature in ISO/IEC 9075-2:2023. It first appeared in the 2008 edition.

You can’t catch up on 20 years of SQL evolution in one day. Subscribe the newsletter via E-Mail, Bluesky or RSS to gradually catch up and to keep modern-⁠sql.com on your radar.

About the Author

Photo of Markus Winand

Markus Winand provides insights into SQL and shows how different systems support it at modern-sql.com. Previously he made use-the-index-luke.com, which is still actively maintained. Markus can be hired as trainer, speaker and consultant via winand.at.

Buy the Book

Cover of “SQL Performance Explained”: Squirrel running on grass

The essence of SQL tuning in 200 pages

Buy now!
(paperback and/or PDF)

Paperback also available at Amazon.com.

Hire Markus

Markus offers SQL training and consulting for developers working at companies of all sizes.
Learn more »

Footnotes

  1. Does not use union, except or intersect (ISO/IEC 9075-2:2023 §7.17 SR 26di1).

  2. But no subqueries and no <set function specifications>

Connect with Markus Winand

Subscribe mailinglistsSubscribe the RSS feedMarkus Winand on LinkedInMarkus Winand on XINGMarkus Winand on MastodonMarkus Winand on Bluesky
Copyright 2015-2026 Markus Winand. All righs reserved.
Legal | Contact | NO WARRANTY | Trademarks | Privacy and GDPR