diff options
Diffstat (limited to 'doc/src/sgml/ref/call.sgml')
| -rw-r--r-- | doc/src/sgml/ref/call.sgml | 26 |
1 files changed, 22 insertions, 4 deletions
diff --git a/doc/src/sgml/ref/call.sgml b/doc/src/sgml/ref/call.sgml index abaa81c78b..9e83a77b7c 100644 --- a/doc/src/sgml/ref/call.sgml +++ b/doc/src/sgml/ref/call.sgml @@ -55,9 +55,24 @@ CALL <replaceable class="parameter">name</replaceable> ( [ <replaceable class="p <term><replaceable class="parameter">argument</replaceable></term> <listitem> <para> - An input argument for the procedure call. - See <xref linkend="sql-syntax-calling-funcs"/> for the full details on - function and procedure call syntax, including use of named parameters. + An argument expression for the procedure call. + </para> + + <para> + Arguments can include parameter names, using the syntax + <literal><replaceable class="parameter">name</replaceable> => <replaceable class="parameter">value</replaceable></literal>. + This works the same as in ordinary function calls; see + <xref linkend="sql-syntax-calling-funcs"/> for details. + </para> + + <para> + Arguments must be supplied for all procedure parameters that lack + defaults, including <literal>OUT</literal> parameters. However, + arguments matching <literal>OUT</literal> parameters are not evaluated, + so it's customary to just write <literal>NULL</literal> for them. + (Writing something else for an <literal>OUT</literal> parameter + might cause compatibility problems with + future <productname>PostgreSQL</productname> versions.) </para> </listitem> </varlistentry> @@ -101,7 +116,10 @@ CALL do_db_maintenance(); <title>Compatibility</title> <para> - <command>CALL</command> conforms to the SQL standard. + <command>CALL</command> conforms to the SQL standard, + except for the handling of output parameters. The standard + says that users should write variables to receive the values + of output parameters. </para> </refsect1> |