From 5ec6b7f1b87f0fa006b8e08a11cd4e99bcb67358 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 1 Oct 2011 14:01:46 -0400 Subject: Improve generated column names for cases involving sub-SELECTs. 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 --- doc/src/sgml/ref/select.sgml | 5 +++-- doc/src/sgml/syntax.sgml | 6 +++--- 2 files changed, 6 insertions(+), 5 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml index 7fb52833e8a..636435fe1d8 100644 --- a/doc/src/sgml/ref/select.sgml +++ b/doc/src/sgml/ref/select.sgml @@ -758,8 +758,9 @@ UNBOUNDED FOLLOWING If you do not specify a column name, a name is chosen automatically by PostgreSQL. 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 - ?columnN? 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 + ?column?. diff --git a/doc/src/sgml/syntax.sgml b/doc/src/sgml/syntax.sgml index 9119b60792e..5ea755c5725 100644 --- a/doc/src/sgml/syntax.sgml +++ b/doc/src/sgml/syntax.sgml @@ -2109,9 +2109,9 @@ SELECT ARRAY[]::integer[]; bracketed) subquery. For example: SELECT ARRAY(SELECT oid FROM pg_proc WHERE proname LIKE 'bytea%'); - ?column? -------------------------------------------------------------- - {2011,1954,1948,1952,1951,1244,1950,2005,1949,1953,2006,31} + array +----------------------------------------------------------------------- + {2011,1954,1948,1952,1951,1244,1950,2005,1949,1953,2006,31,2412,2413} (1 row) The subquery must return a single column. The resulting -- cgit v1.2.3