Oracle Database executes all triggers of the same type before executing triggers of a different type.If you have multiple triggers of the same type on a single table, then Oracle Database chooses an arbitrary order to execute these triggers.Triggers can be: Trigger names must be unique with respect to other triggers in the same schema.Trigger names do not need to be unique with respect to other schema objects, such as tables, views, and procedures.
sal_diff); END; / keyword if you want the trigger to query or change the same table, because triggers can only do that after the initial changes are applied and the table is back in a consistent state.
Your package should include a counter variable to detect this situation.
A relational database does not guarantee the order of rows processed by a SQL statement.
Because the trigger uses the clause, it might be executed multiple times, such as when updating or deleting multiple rows.
You might omit this clause if you just want to record the fact that the operation occurred, but not examine the data for each row.