Re: [BUGS] documentation bug - behave of NEW a OLD in plpgsql's triggers

Hello

2011/5/6 Josh Kupershmidt <schmiddy(at)gmail(dot)com>:
> [Moving to -docs]
>
> On Mon, May 2, 2011 at 12:00 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> Hello
>>
>> one czech user reported a bug in documentation -
>> http://www.postgresql.org/docs/8.4/static/plpgsql-trigger.html
>>
>> NEW
>>
>>    Data type RECORD; variable holding the new database row for
>> INSERT/UPDATE operations in row-level triggers. This variable is NULL
>> in statement-level triggers and for DELETE operations.
>> OLD
>>
>>    Data type RECORD; variable holding the old database row for
>> UPDATE/DELETE operations in row-level triggers. This variable is NULL
>> in statement-level triggers and for INSERT operations.
>>
>> It isn't correct. NEW is not declared in DELETE trigger, OLD isn't
>> declared in INSERT
>
> If I've understood you correctly, the problem is that the docs claim
> that the variables are defined with a value of NULL, when in fact they
> are undefined. For example, if you try to use variable NEW in a delete
> trigger, you'll get an error message like:
> |  ERROR:  record "new" is not assigned yet
> |  DETAIL:  The tuple structure of a not-yet-assigned record is indeterminate.
>
> How about a doc tweak like the attached?

it is correct

Regards

Pavel Stehule

>
> Josh
>