| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Cc: | KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Triggers on columns |
| Date: | 2009-09-03 11:44:53 |
| Message-ID: | 1251978293.4154.2.camel@fsopti579.F-Secure.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-09-03 11:57:09 | Re: Triggers on columns |
| Previous Message | Magnus Hagander | 2009-09-03 11:32:24 | Re: Fwd: Copy out wording |