When a trigger is associated to a view, the base table triggers are normally enabled.
In PL/SQL, a trigger cannot be directly associated with a view. Triggers are typically associated with tables and are used to automatically execute a set of PL/SQL statements in response to specific events on the table, such as INSERT, UPDATE, or DELETE operations.
Views in PL/SQL are virtual tables created by a query. They don’t store data themselves but provide a way to represent the result of a query. Since views don’t have the same underlying physical structure as tables, triggers cannot be directly associated with them.
If you need to perform certain actions when data is manipulated through a view, you might consider using triggers on the underlying tables instead. The triggers can then handle the necessary logic when changes are made to the tables, and those changes are reflected in the view.
In summary, triggers are associated with tables, not views, in PL/SQL.