RE: Downside to SQL Triggers?

["Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>]

Can I assume that the lack of responses means that most haven't used
them, and those that have haven't experienced any problems?

-Walden

------------
Walden H Leverich III
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com
 Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Walden H. Leverich
Sent: Thursday, November 17, 2005 11:38 AM
To: Midrange Systems Technical Discussion
Subject: Downside to SQL Triggers?

Anyone know of a downside to creating triggers with SQL? I don't mean
HLL triggers that have embedded SQL, I'm talking about creating triggers
with the CREATE TRIGGER sql statement. 
 
For some things it might make sense to use HLLs for the trigger, but for
many triggers -- especially those that update one file based on a change
in another, the SQL triggers seem to be obvious candidates.
 
-Walden
 
------------
Walden H Leverich III
Tech Software
(516) 627-3800 x11
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com <blocked::http://www.techsoftinc.com/> 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)

 
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.