Skip to Main Content

SQL & PL/SQL

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

DB Triggers

Dairy LandMar 29 2016 — edited Mar 30 2016

I've seen people that are dead against database triggers. I agree with them to certain extent, in that, a poorly written trigger logic (with calls to data intensive DML queries) can cause performance bottlenecks.  But to categorically deny its use, seems to be not selling with me and puts in a place where I have to argue for it.  Am I missing anything? Are DB triggers really a bad idea?

Here is an example: Any time a Purchase Order is approved, I want to send an email notification to all people involved in the approval hierarchy.

The trigger will flag a change to authorization_status column in po_headers_all table and be done with.  This flag will then kick off a job that picks up the approval hierarchy and build a email list and notify them.


What would be the best way to accomplish real time notification of an approved PO?

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Apr 27 2016
Added on Mar 29 2016
12 comments
2,174 views