Re: Bug in triggers - Mailing list pgsql-bugs

From Pavel Stehule
Subject Re: Bug in triggers
Date
Msg-id 162867791003090731na77a59amf765cdfee7efa003@mail.gmail.com
Whole thread Raw
In response to Re: Bug in triggers  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bug in triggers  (Chris Travers <chris@metatrontech.com>)
List pgsql-bugs
2010/3/9 Tom Lane <tgl@sss.pgh.pa.us>:
> Robert Haas <robertmhaas@gmail.com> writes:
>> What seems odd to me is that NEW is apparently some other kind of
>> thing that is not the same kind of thing as the row variable.
>
> NEW is a record variable, not a row variable. =C2=A0In this context that's
> sensible because its actual rowtype is unspecified by the function text.
> The implications for row-null handling aren't obvious though :-(
>

is it necessary definition there? This is defined well from context.

regards
Pavel Stehule

> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0regards, tom lane
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug in triggers
Next
From: Tom Lane
Date:
Subject: Re: duplicate key violates unique contraint on pg_type_typname_nsp_index