Our technologist looks at trigger maintenance and implementation challenges.
Those of you who frequent the asktom.Web site know that I have an aversion to triggers.
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from Tech Target experts.
I have two primary reasons for avoiding triggers: Hopefully the first reason to avoid triggers, the maintenance headache, is fairly easy to see.
Suppose you are working on someone else’s project, because you have inherited someone else’s work. When you run an update and see “1 row processed,” 500 other things may also have happened.
BTW, I wasn't sure what you meant by "seeded" versus "custom".
We created the view from scratch based on three existing tables.
Once upon a time, a long time ago, I thought triggers were the coolest thing ever and I used (and abused) them heavily.
Now, whenever possible, I will go very far out of my way to avoid a trigger.
You can create a view to be inherently updatable, or you can create an INSTEAD OF trigger on any view to make it updatable.
To learn whether and in what ways the columns of an inherently updatable view can be modified, query the USER_UPDATABLE_COLUMNS data dictionary view.
Powerful desktop applications delivered with the easy and scalability of a web applications.
From the Oracle 10g SQL Reference: Notes on Updatable Views An updatable view is one you can use to insert, update, or delete base table rows.
In this guide, the Oracle Forms application is first analyzed for its components, and then a similar analysis of the Visual Basic . Strategies for migrating from Oracle Forms to Visual Basic . A detailed discussion on how to perform the migration is beyond the scope of this guide.