From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Doc: improve documentation about composite-value usage. |
Date: | 2016-11-22 22:56:58 |
Message-ID: | E1c9Jzm-0005OX-Qg@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Doc: improve documentation about composite-value usage.
Create a section specifically for the syntactic rules around whole-row
variable usage, such as expansion of "foo.*". This was previously
documented only haphazardly, with some critical info buried in
unexpected places like xfunc-sql-composite-functions. Per repeated
questions in different mailing lists.
Discussion: <16288(dot)1479610770(at)sss(dot)pgh(dot)pa(dot)us>
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/e1320266edd7df53c60af10b4c33ab2754278b3e
Modified Files
--------------
doc/src/sgml/queries.sgml | 3 +-
doc/src/sgml/rowtypes.sgml | 214 +++++++++++++++++++++++++++++++++++++++++++--
doc/src/sgml/syntax.sgml | 16 ++--
doc/src/sgml/xfunc.sgml | 70 +++------------
4 files changed, 231 insertions(+), 72 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-11-22 23:07:54 | pgsql: Doc: in back branches, don't call it a row constructor if it isn |
Previous Message | Robert Haas | 2016-11-22 20:50:47 | pgsql: Code review for commit 274bb2b3857cc987cfa21d14775cae9b0dababa5. |