Re: calling plsql with invoker rights from trigger

Mark Bole <makbo_at_pacbell.net> wrote in

> Are you saying that this would be much better as a DBMS_ALERT, rather
> than a trigger? The LDAP update should be concurrent with the table
> update, although if it fails it isn't fatal.

Mark, I'm saying "WHAT IS A TRANSACTION?".

Think about the ACID properties and then tell me whether or not to make a transaction reliant on the successful completion of sendmail code, passes the ACID test?

I'm saying "WHAT ABOUT PERFORMANCE?". What are the overheads of that code in the trigger that has *NOTHING* to do with maintaining data integrity? When will developers start to think about writing scalable code!?

Updating an LDAP server via a trigger - that to me is walking a very thin line. If the LDAP update fails, what then? Do you rollback the insert? Do you commit, causing now an inconsistency between the db and LDAP servers? Or do you rather use another mechanism that can provide the consistency and management of keeping your EMP table and LDAP server in sync?

I would say the latter. In which case a trigger is most certainly not the right tool for updating the LDAP server.

--
Billy