strategy for recompiling when trigger depends on package
Hello,
I am using 11g Enterprise 11.2
I have a package that depends on many columns in many tables. So, if one of the columns is changed in some way, the package is invalidated. This is usually not a problem, because the next time I call a procedure in the package, it is automatically recompiled.
However, the problem occurs because a procedure in the package is called from within a trigger. As far as I understand, triggers don't recompile automatically when DML is issued that uses that trigger.
What is a strategy to handle this type of situation? A column change could invalidate a package, which could invalidate a trigger, which could mess up some DML. Should all people on team recompile triggers/packages every time an alter table is issued?
Or, is there a better strategy for handling this type thing? Perhaps a more automated solution?
Thanks.
Edited by: dougd_unc on Sep 4, 2010 10:25 PM