There are misprints in postgres doc., in :
Chapter 10. PL/pgSQL - SQL Procedural Language (c40914117.htm) Statements ... (resulting in a PL/pgSQL internal SELECT). But there are cases where someone isn't interested int -----------------------------------------(have to be)--> But there are cases where someone isn't interested in the functions result. RAISE level format'' --(have to be)--> RAISE level 'format'
This commit is contained in:
parent
26e0321191
commit
9a342d2035
@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/plsql.sgml,v 2.14 2001/01/13 23:58:55 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/plsql.sgml,v 2.15 2001/01/17 16:34:34 momjian Exp $
|
||||
-->
|
||||
|
||||
<chapter id="plsql">
|
||||
@ -472,7 +472,7 @@ END IF;
|
||||
database return a value. Thus, the normal way to call a function
|
||||
is to execute a SELECT query or doing an assignment (resulting
|
||||
in a PL/pgSQL internal SELECT). But there are cases where someone
|
||||
isn't interested int the functions result.
|
||||
isn't interested in the functions result.
|
||||
<programlisting>
|
||||
PERFORM <replaceable>query</replaceable>
|
||||
</programlisting>
|
||||
@ -564,7 +564,7 @@ RETURN <replaceable>expression</replaceable>
|
||||
can throw messages into the <productname>Postgres</productname>
|
||||
elog mechanism.
|
||||
<programlisting>
|
||||
RAISE <replaceable class="parameter">level</replaceable> <replaceable class="parameter">format</replaceable>'' [, <replaceable class="parameter">identifier</replaceable> [...]];
|
||||
RAISE <replaceable class="parameter">level</replaceable> '<replaceable class="parameter">format</replaceable>' [, <replaceable class="parameter">identifier</replaceable> [...]];
|
||||
</programlisting>
|
||||
Inside the format, "<literal>%</literal>" is used as a placeholder for the
|
||||
subsequent comma-separated identifiers. Possible levels are
|
||||
|
Loading…
Reference in New Issue
Block a user