Re: 2 b4 update triggers, what is fire sequence?

Following up on Michael, 12 Feb 2003:

> So ......
>
> you're saying it's possible .....
>
> ;-)

Hehehe! You're pushing it!...... :D

It might be possible. But it is not RELIABLE. You can have it all working in the order you like and then one day you do an export/import or some other op that reorgs the dictionary and boink! - all heck breaks loose.

If your COTS trigger is b4 update, I'd work extra hard to make your site triggers after-update? That is guaranteed to make things work like you want.

If you however have to create your site trigger to run b4 the COTS, you're up against a hard rock.

If the application people did the right thing, then maybe there is a way out:

If their code executes in a procedure or package, called by the trigger, then it's dirt easy:
drop the trigger, re-create it as your own package that then calls your code wherever and calls their package wherever.

If they didn't do the right thing, then send them a nasty, vicious letter telling them to start coding defensively or else! Or sell them on your idea? ;)

There *IS* a reason why a lot of designers recommend that triggers in ANY database never have in-line code: they should always call a stored package to do their work. Your case is a perfect example of why.

-- 
Cheers
Nuno Souto
nsouto_at_optusnet.com.au.nospam