Q

Avoiding mutation errors while writing triggers

What is a mutation error and how do I avoid mutation errors while writing triggers?

What is a mutation error and how do I avoid mutation errors while writing triggers?
A trigger fires when the underlying table experiences some sort of DML operation. If the trigger then makes another DML change to the same table, this will cause the trigger to fire again, which means another change and the trigger firing again . . . where does it end? In a nutshell, a mutating table happens when a trigger keeps firing on only one DML operation.

This link describes mutating tables in more detail as well as instructions on how to avoid it.

This was last published in August 2006

Dig Deeper on Oracle database design and architecture

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide

SearchDataCenter

SearchContentManagement

SearchFinancialApplications

Close