Is it possible to temporarily disable an after update trigger
from within itself to prevent recursion where the trigger
causes further edits to the same table?

In my particular case it seems difficult to solve this by
just looking at the incoming field values and bypassing the
offending code.

Thanks,
Steve