Re: Future of Triggers

> The instead OF triggers require you to update through the view directly to
> fire the trigger. I was thinking more of when a TABLE is updated, all of the
> views over that table are checked and any trigger that is associated with it
> is fired.

Isn't that what a trigger on the table does? Why would you want a trigger to fire over all views built on a table when a table is updated? Instead, the trigger on the table handles everything. It just seems to make more sense to me that way.

Just my 3.14159265 cents worth,
Brian

-- 
========================================
Brian Peasland
Raytheons Systems at
  USGS EROS Data Center
These opinions are my own and do not
necessarily reflect the opinions of my 
company!
========================================