1
0
mirror of https://github.com/postgres/postgres.git synced 2025-06-08 22:02:03 +03:00

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
This commit is contained in:
Bruce Momjian 2011-09-06 22:54:18 -04:00
parent 6117526b5b
commit e4d59f3536

View File

@ -3282,8 +3282,8 @@ 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 not defined in statement-level triggers
and for <command>DELETE</command> operations. or <command>DELETE</command> operations.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -3294,8 +3294,8 @@ 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 not defined in statement-level triggers
and for <command>INSERT</command> operations. or <command>INSERT</command> operations.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>