Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 0729271

Browse files
committed
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
1 parent d55f1b8 commit 0729271

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/src/sgml/plpgsql.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3403,7 +3403,7 @@ RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
34033403
<para>
34043404
Data type <type>RECORD</type>; variable holding the new
34053405
database row for <command>INSERT</>/<command>UPDATE</> operations in row-level
3406-
triggers. This variable is <symbol>NULL</symbol> in statement-level triggers
3406+
triggers. This variable is unassigned in statement-level triggers
34073407
and for <command>DELETE</command> operations.
34083408
</para>
34093409
</listitem>
@@ -3415,7 +3415,7 @@ RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
34153415
<para>
34163416
Data type <type>RECORD</type>; variable holding the old
34173417
database row for <command>UPDATE</>/<command>DELETE</> operations in row-level
3418-
triggers. This variable is <symbol>NULL</symbol> in statement-level triggers
3418+
triggers. This variable is unassigned in statement-level triggers
34193419
and for <command>INSERT</command> operations.
34203420
</para>
34213421
</listitem>

0 commit comments

Comments
 (0)