Hi,
Is there any way to prevent a trigger from firing during a COPY operation?
We have a case where we dump the records from a table, truncate it, and
copy the records back in. However, there is a trigger on that table,
which will insert a record in a logging table. Is there a way to prevent
this trigger from firing during the COPY FROM process?
Just a little more background, I tried to make the function a little
more intelligent with OLD and NEW, but in the case of an INSERT, there
is no OLD, so there is no comparison.
Regards
- Ericson Smith
eric@did-it.com
Did-it.com
The Search Campaign Specialists
