--On 23. September 2010 08:59:32 +0100 Dean Rasheed
<dean.a.rash...@gmail.com> wrote:
Yes, I agree. To me this is the least surprising behaviour. I think a
more common case would be where the trigger computed a value (such as
the 'last updated' example). The executor doesn't have any kind of a
handle on the row inserted by the trigger, so it has to rely on the
function return value to support RETURNING.
I didn't mean to forbid it altogether, but at least to document
explicitely, that the trigger returns a VIEW's NEW tuple, not the one of
the base table (and may modify it). But you've already adressed this in
your doc patches, so nothing to worry about further.
--
Thanks
Bernd
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
