Re: Trigger question: ROW or STATEMENT?
От | Patrick Hatcher |
---|---|
Тема | Re: Trigger question: ROW or STATEMENT? |
Дата | |
Msg-id | OF4DFBDD2B.BB299BE4-ON88257101.00770BF4-88257101.007D38A2@FDS.com обсуждение исходный текст |
Ответ на | Re: Trigger question: ROW or STATEMENT? (Doug McNaught <doug@mcnaught.org>) |
Ответы |
Re: Trigger question: ROW or STATEMENT?
|
Список | 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@mcnaught.or g> To Patrick Hatcher 01/25/06 01:36 PM <PHatcher@macys.com> cc pgsql-general@postgresql.org Subject Re: [GENERAL] Trigger question: ROW or STATEMENT? Patrick Hatcher <PHatcher@macys.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
В списке pgsql-general по дате отправления: