| From: | Patrick Hatcher <PHatcher(at)macys(dot)com> |
|---|---|
| To: | Doug McNaught <doug(at)mcnaught(dot)org> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Trigger question: ROW or STATEMENT? |
| Date: | 2006-01-25 22:47:45 |
| Message-ID: | OF4DFBDD2B.BB299BE4-ON88257101.00770BF4-88257101.007D38A2@FDS.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Would I gain any advantage by changing to it to fire after the insert?
thanks again for the help
Patrick Hatcher
Development Manager Analytics/MIO
Macys.com
415-422-1610
Doug McNaught
<doug(at)mcnaught(dot)or
g> To
Patrick Hatcher
01/25/06 01:36 PM <PHatcher(at)macys(dot)com>
cc
pgsql-general(at)postgresql(dot)org
Subject
Re: [GENERAL] Trigger question:
ROW or STATEMENT?
Patrick Hatcher <PHatcher(at)macys(dot)com> writes:
> Here is the trigger the way it is currently written. I add some
additional
> information from another table:
If you're modifying each row before it goes in, it should definitely
be a FOR EACH ROW trigger.
-Doug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Crozier | 2006-01-25 23:40:38 | pgstattuple output? |
| Previous Message | Jim Buttafuoco | 2006-01-25 22:08:48 | Re: My very first PL/pgSQL procedure... |