From: Tom Lane Date: Tue, 22 Nov 2016 23:07:43 +0000 (-0500) Subject: Doc: in back branches, don't call it a row constructor if it isn't really. X-Git-Tag: REL9_6_2~121 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=51aebcd78a4a0674737319a804ff761800fa6830;p=postgresql 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> --- diff --git a/doc/src/sgml/ref/update.sgml b/doc/src/sgml/ref/update.sgml index c50434f85f..e80cf9cb78 100644 --- a/doc/src/sgml/ref/update.sgml +++ b/doc/src/sgml/ref/update.sgml @@ -422,9 +422,9 @@ UPDATE films SET kind = 'Dramatic' WHERE CURRENT OF c_films; According to the standard, the source value for a parenthesized sub-list of column names can be any row-valued expression yielding the correct number of columns. PostgreSQL only allows the source - value to be a parenthesized list of expressions (a row constructor) or a + value to be a parenthesized list of expressions or a sub-SELECT. An individual column's updated value can be - specified as DEFAULT in the row-constructor case, but not + specified as DEFAULT in the list-of-expressions case, but not inside a sub-SELECT.