| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Triggers on columns |
| Date: | 2009-09-03 11:57:09 |
| Message-ID: | CF636597-32B5-410B-A3EC-A315D734F049@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sep 3, 2009, at 7:44 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On Thu, 2009-09-03 at 16:25 +0900, Itagaki Takahiro wrote:
>> I'd like to check conditions by comparing actual values but not
>> a target of UPDATE statement because I think almost user expects
>> the former behavior. Unmodified UPDATE-targets are common case
>> if we use a framework that generates SQL statements internally.
>
> The SQL standard specifies that a trigger is fired if the column is
> mentioned in the UPDATE statement, independent of whether the value is
> actually changed through the update.
That is thorougly bizarre, IMO.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2009-09-03 12:15:36 | Re: Triggers on columns |
| Previous Message | Peter Eisentraut | 2009-09-03 11:44:53 | Re: Triggers on columns |