Another upvote. I like the idea in the item, allthough I'd like just implementing BEFORE triggers even better.
However, I do not share your dislike for INSTEAD OF triggers. They are a great tool for some specific purposes. I have used them to expose views as if they were the base tables, hiding the actual base tables, and allowing full updatability even when SQL Server itself would consider the view non-updatable or misunderstand how to change the base tables to correspond to the actual change,
You misunderstand my dislike for "Instead Of" triggers. As you say, they ARE great for specific purposes. A perfect example is when the target of an insert is actually an updateable view built for one reason or another. Still, you have to control everything there instead of just what you need to control, whatever that may be.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
When you put the right degree of spin on it, the number 3|8
is also a glyph that describes the nature of a DBAs job. 😉
How to post code problems
Create a Tally Function (fnTally)