Properly document the existance of OLD/NEW trigger pl/pgsql trigger

fields.

Backpatch to 9.0 and 9.1.

Report from Pavel Stehule, patch from Josh Kupershmidt
This commit is contained in:
Bruce Momjian 2011-09-06 22:54:16 -04:00
parent d858abfdfd
commit 39039e6d7a

View File

@ -3373,8 +3373,8 @@ RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
<para>
Data type <type>RECORD</type>; variable holding the new
database row for <command>INSERT</>/<command>UPDATE</> operations in row-level
triggers. This variable is <symbol>NULL</symbol> in statement-level triggers
and for <command>DELETE</command> operations.
triggers. This variable is not defined in statement-level triggers
or <command>DELETE</command> operations.
</para>
</listitem>
</varlistentry>
@ -3385,8 +3385,8 @@ RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
<para>
Data type <type>RECORD</type>; variable holding the old
database row for <command>UPDATE</>/<command>DELETE</> operations in row-level
triggers. This variable is <symbol>NULL</symbol> in statement-level triggers
and for <command>INSERT</command> operations.
triggers. This variable is not defined in statement-level triggers
or <command>INSERT</command> operations.
</para>
</listitem>
</varlistentry>