Disable or drop trigger, is there a difference?
651980Sep 2 2009 — edited Sep 2 2009Firstly let me explain the scenario, a developer created a trigger on a TABLE owned by another schema to insert into his own schema. Anyway it did not work and gave him various errors through TOAD that I do not have copies of. He disabled the trigger but the errors continued. It was only when the trigger was dropped that the error ceased. My question is Is there something different between disabling a trigger and dropping it apart from the obvious? I also have to explain that this is on a very old database version 7.3.4.4.0 on solaris. I do know why disabling it would not mean it was ignored therefore effectively acting as if it did not exist at all much like if it was dropped from the database. Any suggestions?
The trigger was eventually recreated and a public synonym creation on the table that was to be inserted into solved the errors. But why did disabling the trigger still mean errors where thrown out.
Edited by: user648977 on 02-Sep-2009 00:32