database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-02 11:44:50 +03:00
Code

Clarify CREATE FUNCTION documentation about handling of typmods.

Browse Source 
The previous text was a bit misleading, as well as unnecessarily vague
about what information would be discarded.  Per gripe from Craig Skinner.
This commit is contained in:
Tom Lane 2013-11-13 13:26:33 -05:00
parent d147aedbfe
commit 42f8e268c9
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/src/sgml/ref/create_function.sgml
View File

@ -579,12 +579,13 @@ CREATE FUNCTION foo(int, int default 42) ...
<para> <para>
The full <acronym>SQL</acronym> type syntax is allowed for The full <acronym>SQL</acronym> type syntax is allowed for
input arguments and return value. However, some details of the declaring a function's arguments and return value. However,
type specification (e.g., the precision field for parenthesized type modifiers (e.g., the precision field for
type <type>numeric</type>) are the responsibility of the type <type>numeric</type>) are discarded by <command>CREATE FUNCTION</>.
underlying function implementation and are silently swallowed Thus for example
(i.e., not recognized or <literal>CREATE FUNCTION foo (varchar(10)) ...</>
enforced) by the <command>CREATE FUNCTION</command> command. is exactly the same as
<literal>CREATE FUNCTION foo (varchar) ...</>.
</para> </para>
<para> <para>