pgsql: Doc: in back branches, don't call it a row constructor if it isn - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Doc: in back branches, don't call it a row constructor if it isn
Date
Msg-id E1c9KAM-0005aZ-SJ@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Doc: in back branches, don't call it a row constructor if it isn't really.

Before commit 906bfcad7, we were not actually processing the righthand
side of a multiple-column assignment in UPDATE as a row constructor:
it was just a parenthesized list of expressions.  Call it that rather
than risking confusion by people who would expect the documented behaviors
of row constructors to apply.

Back-patch to 9.5; before that, the text correctly described the construct
as a "list of independent expressions".

Discussion: <16288.1479610770@sss.pgh.pa.us>

Branch
------
REL9_6_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/51aebcd78a4a0674737319a804ff761800fa6830

Modified Files
--------------
doc/src/sgml/ref/update.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Doc: in back branches, don't call it a row constructor if it isn
Next
From: "David G. Johnston"
Date:
Subject: Re: pgsql: Doc: improve documentation about composite-value usage.