pgsql: Improve generated column names for cases involving sub-SELECTs.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Improve generated column names for cases involving sub-SELECTs.
Date: 2011-10-01 18:01:57
Message-ID: E1RA3sr-00056J-36@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/5ec6b7f1b87f0fa006b8e08a11cd4e99bcb67358

Modified Files
--------------
doc/src/sgml/ref/select.sgml | 5 ++-
doc/src/sgml/syntax.sgml | 6 ++--
src/backend/parser/parse_target.c | 42 ++++++++++++++++++++++++++++++
src/test/regress/expected/aggregates.out | 6 ++--
src/test/regress/expected/subselect.out | 12 ++++----
src/test/regress/expected/with.out | 4 +-
6 files changed, 59 insertions(+), 16 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2011-10-02 20:50:35 pgsql: Restructure error handling in reading of postgresql.conf.
Previous Message Bruce Momjian 2011-10-01 14:02:56 pgsql: In pg_upgrade, remove unnecessary local variable.