Re: Odd plpgsql behaviour

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mike Rylander <mrylander(at)gmail(dot)com>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Odd plpgsql behaviour
Date: 2004-11-15 15:29:46
Message-ID: 7985.1100532586@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mike Rylander <mrylander(at)gmail(dot)com> writes:
> IIRC, the reason for this is that the entire IF test is passed to the
> SQL engine as a SELECT statement after replacing the TG_* identifiers
> with their respective values.
> In this case, since OLD.name does not exist during INSERT it cannot be
> replaced. Perhaps someone else can shed a little more light on this.

Nope, that's about all there is to say about it ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-11-15 15:41:50 Re: psql \e broken again
Previous Message Oleg Bartunov 2004-11-15 15:24:56 Re: 8.0 press release