Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 39039e6

Browse files
committed
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
1 parent d858abf commit 39039e6

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/src/sgml/plpgsql.sgml

+4-4
Original file line numberDiff line numberDiff line change
@@ -3373,8 +3373,8 @@ RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
33733373
<para>
33743374
Data type <type>RECORD</type>; variable holding the new
33753375
database row for <command>INSERT</>/<command>UPDATE</> operations in row-level
3376-
triggers. This variable is <symbol>NULL</symbol> in statement-level triggers
3377-
and for <command>DELETE</command> operations.
3376+
triggers. This variable is not defined in statement-level triggers
3377+
or <command>DELETE</command> operations.
33783378
</para>
33793379
</listitem>
33803380
</varlistentry>
@@ -3385,8 +3385,8 @@ RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
33853385
<para>
33863386
Data type <type>RECORD</type>; variable holding the old
33873387
database row for <command>UPDATE</>/<command>DELETE</> operations in row-level
3388-
triggers. This variable is <symbol>NULL</symbol> in statement-level triggers
3389-
and for <command>INSERT</command> operations.
3388+
triggers. This variable is not defined in statement-level triggers
3389+
or <command>INSERT</command> operations.
33903390
</para>
33913391
</listitem>
33923392
</varlistentry>

0 commit comments

Comments
 (0)