|
Comments
|
|
Interesting!
|
|
|
Simple and to the point!
|
|
Thad Moorer on
10/20/2009
Very useful and practical concept.
|
|
|
Good one
|
|
|
This was very useful as I need to soon create my first Intead of triggers.
Is it possible to get a copy of the SQL used to define the trigger in this example?
|
|
|
Can you provide an example of when one might use this? I would think that most times one would WANT to know if an insert was NOT occurring.
|
|
|
Where is this useful?
|
|
|
very illustrative! thanks!
|
|
|
Great Video
|
|
|
great.
|
|
|
Good
|
|
|
The video does a good job of presenting the how-to but the example does not use a good case scenario. If you are not going to allow the insert then what do you return to the user?
|
|
|
I wasnt sure initialy why you'd want to put the trigger on a view instead of directly onto the table. It also raised the question, can you do *after* triggers on a view. But overall it was a superb and thought provoking coverage. Thanks again.
|
|
A Alagu Ganesh on
10/14/2010
Good
|
|
|
love it - have never done a trigger based on a view - must rememer this one
|
|
|
Should show insert, update, and delete over a view over a join.
|