I think Steve is probably a little more precise
in his statement. But there are definitely cases
where using before-row triggers is more expensive
that using after-row triggers to do the same job.
The cost appears as extra current mode gets
and redo log generation.
Thomas Kyte has a
In Steve Adams sample of performance report there is a suggestion to use
trigger after row update instead of before row update because it will halve
the number of redo records created for row locks. Anybody has diferent
opinion?
Alex Hillman
--
Please see the official ORACLE-L FAQ:
