Case $9-1$: Mapping the Flow of Database Triggers$$After you learn how to create triggers, you realize that one statement can end up firing off a number of triggers. Not only can you have multiple triggers attached to a single table, but also a trigger can perform DML operations that might affect other tables and fire off other triggers. To prevent this problem, you might be able to combine triggers to make your code clearer and easier to maintain. For example, if you have one trigger for an INSERT statement on the BB$\_$PRODUCT table and another for an UPDATE statement on the BB$\_$PRODUCT table, you might want to combine them into one trigger and use conditional predicates. In addition, triggers that run DML statements that could fire off additional triggers could lead to a mutating table error. However, this error might not be apparent unless you identify the flow of trigger processing and associated objects.