Properly document that NEW is unassigned in plpgsql for DELETE (not

NULL), and OLD is unassigned for INSERT, and NEW/OLD are unassigned (not
NULL) for statement-level triggers.

Per report from Pavel Stehule
This commit is contained in:
Bruce Momjian 2012-08-15 20:29:58 -04:00
parent d55f1b852d
commit 0729271adf

View File

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