database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-22 21:53:06 +03:00
Code Activity

Improve generated column names for cases involving sub-SELECTs.

Browse Source 
We'll now use "exists" for EXISTS(SELECT ...), "array" for ARRAY(SELECT
...), or the sub-select's own result column name for a simple expression
sub-select.  Previously, you usually got "?column?" in such cases.

Marti Raudsepp, reviewed by Kyotaro Horiugchi
This commit is contained in:
Tom Lane
2011-10-01 14:01:46 -04:00
parent 878b74e094
commit 5ec6b7f1b8
6 changed files with 59 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/src/sgml/ref/select.sgml
View File

@@ -758,8 +758,9 @@ UNBOUNDED FOLLOWING
If you do not specify a column name, a name is chosen automatically
by <productname>PostgreSQL</productname>. If the column's expression
is a simple column reference then the chosen name is the same as that
column's name; in more complex cases a generated name looking like
<literal>?column<replaceable>N</>?</literal> is usually chosen.
column's name. In more complex cases a function or type name may be
used, or the system may fall back on a generated name such as
<literal>?column?</literal>.
</para>
<para>