Re: Questions about instead of triggers

If colnameA is not present in the update clause you should find that

   :new.colnameA is the same as :old.colnameA

But beware how you write code to check this or you may get caught in the trap of

    (NULL = NULL) is NULL, not TRUE.

You also have the option to write triggers which fire

    INSTEAD OF UPDATE of col1, col2

--

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

Cory Brooks wrote in message <37908D97.F6BB63B2_at_lilly.com>...
>In other words, the new value for a column can be null because it's
>being set to null or because it's omitted from the set clause (i.e.,
>should NOT be changed).
Received on Mon Jul 19 1999 - 06:20:05 CDT