aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2012-08-15 20:29:58 -0400
committerBruce Momjian <bruce@momjian.us>2012-08-15 20:29:58 -0400
commit0729271adf9145900f59ec7a2053695bd551f4b1 (patch)
tree8b68a298453d29c36d6401fd64f6a2f1cb22ed1a
parentd55f1b852d4fe87f2a4d16ea3f0ce11a7019a352 (diff)
downloadpostgresql-0729271adf9145900f59ec7a2053695bd551f4b1.tar.gz
postgresql-0729271adf9145900f59ec7a2053695bd551f4b1.zip
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
-rw-r--r--doc/src/sgml/plpgsql.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index ab408456506..07fba57c0e1 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -3403,7 +3403,7 @@ 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
+ triggers. This variable is unassigned in statement-level triggers
and for <command>DELETE</command> operations.
</para>
</listitem>
@@ -3415,7 +3415,7 @@ 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
+ triggers. This variable is unassigned in statement-level triggers
and for <command>INSERT</command> operations.
</para>
</listitem>