pgsql: Improve documentation about array concat operator vs. underlying

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Improve documentation about array concat operator vs. underlying
Date: 2015-07-09 22:50:48
Message-ID: E1ZDKeW-00049e-Ee@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Improve documentation about array concat operator vs. underlying functions.

The documentation implied that there was seldom any reason to use the
array_append, array_prepend, and array_cat functions directly. But that's
not really true, because they can help make it clear which case is meant,
which the || operator can't do since it's overloaded to represent all three
cases. Add some discussion and examples illustrating the potentially
confusing behavior that can ensue if the parser misinterprets what was
meant.

Per a complaint from Michael Herold. Back-patch to 9.2, which is where ||
started to behave this way.

Branch
------
REL9_4_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/8989a52657332c98fab56de6b86c41d93ea0c621

Modified Files
--------------
doc/src/sgml/array.sgml | 47 +++++++++++++++++++++++++++++++++++++++++------
1 file changed, 41 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2015-07-10 11:50:58 pgsql: Copy-edit the docs changes of OWNER TO CURRENT/SESSION_USER addi
Previous Message Peter Eisentraut 2015-07-09 18:32:39 Re: pgsql: Replace our hacked version of ax_pthread.m4 with latest upstream