See tkyte.blogspot.com/2005/08/, tkyte.blogspot.com/2005/08/part-ii-seeing-restart.html, and tkyte.blogspot.com/2005/09/for details on this behavior.) What this means is that any trigger that invokes many of the UTL_ functions is probably doing it wrong.
The next implementation problem with triggers stems from the fact that developers often do not understand all the nuances of concurrency controls and isolation levels in the database.
Say you have a bit of code or better yet a stored procedure that represents a transaction, and you read it. I get it.” But if you are on a system laden with triggers all over the place, you won’t have gotten it at all—you’ll have gotten it wrong, at best. More than once, I’ve received an e-mail similar to the following (this is a cut-and-paste—I did not make this up): We have a problem when updating a column.
When we update that column (type is varchar2), the update is showing 1,972 rows updated (and we commit after the UPDATE). ” The response back to me was, “Oh, that explains it. We had ‘::= :new.fname
The next implementation problem with triggers stems from the fact that developers often do not understand all the nuances of concurrency controls and isolation levels in the database.
Say you have a bit of code or better yet a stored procedure that represents a transaction, and you read it. I get it.” But if you are on a system laden with triggers all over the place, you won’t have gotten it at all—you’ll have gotten it wrong, at best. More than once, I’ve received an e-mail similar to the following (this is a cut-and-paste—I did not make this up): We have a problem when updating a column.
When we update that column (type is varchar2), the update is showing 1,972 rows updated (and we commit after the UPDATE). ” The response back to me was, “Oh, that explains it. We had ‘::= :new.fname