RE: triggers within commit cycles

["Smith, Nelson" <NSmith@xxxxxxxxxxx>]

One good use of triggers is to prevent any updates EXCEPT through your
defined I/O modules.  In a similar vein, triggers can be used to "soften"
the hard crash that results from a referential constraint violation.

> -----Original Message-----
> From: Joe Pluta [SMTP:joepluta@PlutaBrothers.com]
> Sent: Tuesday, August 21, 2001 1:15 PM
> To:   midrange-l@midrange.com
> Subject:      RE: triggers within commit cycles
>
> I suppose.  Don't ask me, I wouldn't use triggers for business rules.  If
> I
> can write a trigger program, I can write an external I/O module.  The only
> reason to use triggers for business rules is so that you can have things
> like DFU and SQL updates as part of your production systems.
>
> You may be able to guess what I think of that.
>
> Joe
>
>
>


************************************************************************************************************************************************************************************************************
This message originates from Lincare Holdings Inc. It contains information 
which maybe confidential or privileged and is intended only for the individual 
or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use the 
contents of this message.
All personal messages express views solely of the sender, which are not to be 
attributed to Lincare Holdings Inc., and may not be copied or distributed 
without this disclaimer.
If you received this message in error, please notify us immediately at 
MailAdmin@lincare.com or (800) 284-2006.
************************************************************************************************************************************************************************************************************