| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Boxuan Zhai <bxzhai2010(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: MERGE Specification |
| Date: | 2010-08-11 10:17:59 |
| Message-ID: | 1281521879.8340.1.camel@fsopti579.F-Secure.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On fre, 2010-08-06 at 10:28 +0300, Heikki Linnakangas wrote:
> IMO the UPDATE/DELETE/INSERT actions should fire the respective
> statement level triggers, but the MERGE itself should not.
Yes, SQL defines the triggering of triggers as part of the modification
of rows, not as part of any particular statement that causes the
modification.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2010-08-11 10:18:43 | Re: assertions and constraint triggers |
| Previous Message | Pavel Stehule | 2010-08-11 10:00:17 | Re: string_to_array with an empty input string |