aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml/xfunc.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/sgml/xfunc.sgml')
-rw-r--r--doc/src/sgml/xfunc.sgml8
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml
index 9fb2be4aecb..e79c1f29236 100644
--- a/doc/src/sgml/xfunc.sgml
+++ b/doc/src/sgml/xfunc.sgml
@@ -271,7 +271,7 @@ $$ LANGUAGE SQL;
</para>
</sect2>
- <sect2>
+ <sect2 id="xfunc-sql-composite-functions">
<title><acronym>SQL</acronym> Functions on Composite Types</title>
<para>
@@ -492,6 +492,12 @@ SELECT emp.name, emp.double_salary FROM emp;
<literal>double_salary</> isn't a real column of the table.
(You can also emulate computed fields with views.)
</para>
+
+ <para>
+ Because of this behavior, it's unwise to give a function that takes
+ a single composite-type argument the same name as any of the fields of
+ that composite type.
+ </para>
</tip>
<para>