Commit 6334ef86 authored by Tom Lane's avatar Tom Lane

Document that we don't support ORDER BY with general expressions on

the output of UNION/INTERSECT/EXCEPT.
parent 005ad6cd
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.35 2000/12/12 05:07:59 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.36 2001/01/08 21:30:37 tgl Exp $
Postgres documentation Postgres documentation
--> -->
...@@ -616,7 +616,12 @@ SELECT title, date_prod + 1 AS newlen FROM films ORDER BY newlen; ...@@ -616,7 +616,12 @@ SELECT title, date_prod + 1 AS newlen FROM films ORDER BY newlen;
<programlisting> <programlisting>
SELECT name FROM distributors ORDER BY code; SELECT name FROM distributors ORDER BY code;
</programlisting> </programlisting>
A limitation of this feature is that an ORDER BY clause applying to the
result of a UNION, INTERSECT, or EXCEPT query may only specify an output
column name or number, not an expression.
</para>
<para>
Note that if an ORDER BY item is a simple name that matches both Note that if an ORDER BY item is a simple name that matches both
a result column name and an input column name, ORDER BY will interpret a result column name and an input column name, ORDER BY will interpret
it as the result column name. This is the opposite of the choice that it as the result column name. This is the opposite of the choice that
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment