From a443343ccf2d7b105ce550b5746d993151569d93 Mon Sep 17 00:00:00 2001 From: Bruce Momjian <bruce@momjian.us> Date: Tue, 6 Sep 2011 22:54:19 -0400 Subject: [PATCH] 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 --- doc/src/sgml/plpgsql.sgml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml index b3016aed54..ab9fdc0542 100644 --- a/doc/src/sgml/plpgsql.sgml +++ b/doc/src/sgml/plpgsql.sgml @@ -3072,8 +3072,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> @@ -3084,8 +3084,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> -- 2.40.0