Second, they blindly overwrite the NAME attribute in the trigger.If you use a trigger to invoke UTL_HTTP to invoke a service on a Web server, you’ll have invoked that service for an event that never happened.UTL_MAIL, UTL_SMTP, and UTL_TCP all suffer from the same problem: if the transaction that caused the trigger to fire rolls back, they’ll have performed operations that cannot be rolled back.But dealing with incorrect implementation of triggers is another thing.Far too often, just anyone will create a trigger, without understanding the ramifications of doing so.
Second, they blindly overwrite the NAME attribute in the trigger.If you use a trigger to invoke UTL_HTTP to invoke a service on a Web server, you’ll have invoked that service for an event that never happened.UTL_MAIL, UTL_SMTP, and UTL_TCP all suffer from the same problem: if the transaction that caused the trigger to fire rolls back, they’ll have performed operations that cannot be rolled back.But dealing with incorrect implementation of triggers is another thing.Far too often, just anyone will create a trigger, without understanding the ramifications of doing so.Once upon a time, a long time ago, I thought triggers were the coolest thing ever and I used (and abused) them heavily.