Re: TODO: trigger features

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: TODO: trigger features
Date: 2003-08-05 19:15:55
Message-ID: 3F30026B.5080604@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

>Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
>
>
>>- Implement a way to enable triggers to check which columns are affected
>>by the triggering statement.
>>
>>
>
>This can already be done by comparing old and new values, no?
>
No, this is not the case.

UPDATE foo SET x=x, y=y
is different from
UPDATE foo SET y=y
if triggers maintaining x are involved. I had this case, and had to do
quite weird stuff to implement this.

Regards,
Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-08-05 19:21:08 Re: TODO: trigger features
Previous Message Tom Lane 2003-08-05 19:04:53 Re: TODO: trigger features