Introduction
Many times we have the situation where a master
table may be updated and dependent tables are left without a link
back to the master. In this situation a cascade update option would
be a nice one to have. Unfortunately Oracle Corp. doesn't provide
this capability in a native manner so a PL/SQL option must be
developed.
An example of a need for a cascade update would
be in the situation where a dependent table could be dependent on
one or more tables. For example, there may be two types of customer,
one who has bought from us and we have marketing information for and
another that is new to us, may buy from us, but may go with another
vendor. If there are dependent tables (such as an interaction log
that tracks phone calls to and from customers) it would be nice to
be able to switch the dependencies from our new customer table to
our established customer table.
