]> granicus.if.org Git - postgresql/commit
Improve generated column names for cases involving sub-SELECTs.
authorTom Lane <tgl@sss.pgh.pa.us>
Sat, 1 Oct 2011 18:01:46 +0000 (14:01 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Sat, 1 Oct 2011 18:01:46 +0000 (14:01 -0400)
commit5ec6b7f1b87f0fa006b8e08a11cd4e99bcb67358
tree3f178e9a5ffd1683278a94614e2b11779116a983
parent878b74e094a70e660e5ed365a2c4e1b41460515d
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
doc/src/sgml/syntax.sgml
src/backend/parser/parse_target.c
src/test/regress/expected/aggregates.out
src/test/regress/expected/subselect.out
src/test/regress/expected/with.out