database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-19 13:42:17 +03:00
Code Activity

doc: consistently use "structname" and "structfield" markup

Browse Source 
Previously "literal" and "classname" were used, inconsistently, for
SQL table and column names.

Reported-by: Peter Smith

Author: Peter Smith

Discussion: https://postgr.es/m/CAHut+Pvtf24r+bdPgBind84dBLPvgNL7aB+=HxAUupdPuo2gRg@mail.gmail.com

Backpatch-through: master
This commit is contained in:
Bruce Momjian
2025-11-08 09:49:43 -05:00
parent e8bfad4ca8
commit 980a855c5c
33 changed files with 166 additions and 166 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/syntax.sgml
View File

@@ -2430,8 +2430,8 @@ SELECT ROW(1,2.5,'this is a test');
which will be expanded to a list of the elements of the row value,
just as occurs when the <literal>.*</literal> syntax is used at the top level
of a <command>SELECT</command> list (see <xref linkend="rowtypes-usage"/>).
For example, if table <literal>t</literal> has
columns <literal>f1</literal> and <literal>f2</literal>, these are the same:
For example, if table <structname>t</structname> has
columns <structfield>f1</structfield> and <structfield>f2</structfield>, these are the same:
<programlisting>
SELECT ROW(t.*, 42) FROM t;
SELECT ROW(t.f1, t.f2, 42) FROM t;