At 05:23 PM 11/30/2004, GrumpyRain wrote:

>The before update trigger wouldn't have
>written anything to disk yet, but the after update will have written
>the value then roll it back.

It will have written the update to a page in the cache - it's
unlikely - possible - that it will have gone to disk. The undo
log associated with the trigger will almost certainly run around
the cache fixing things up without anything going to disk.

What you can't do in an after update trigger is change the
values stored in the record. Assigning a different value to
new.<fields> has no effect.

Regards,


Ann