Re: Triggers

Interesting coincidence, and timely question...

We are experimenting with using triggers for part of our encryption project, by creating SQL update and insert triggers which would call a UDF or stored procedure to perform the encryption of the field at output time.

However, when you create an SQL trigger the database manager actually creates and compiles an ILE C program which becomes the trigger-handling program on the file.

Please don't let it be true, but does this mean that we would need to have the compilers on our production system in order to create the triggers? This would violate our rules about having a compiler on the production system/LPAR...

Regards,
Steve

----- Original Message ----- From: "Wilt, Charles" <WiltC@xxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, August 24, 2007 6:36 AM
Subject: RE: Triggers

No, he's right.

You can put an SQL trigger on a particular field. Unless that field changes, the trigger won't even
fire.

However, as you and others have pointed out you can check to see which fields have changed in your HLL
trigger program. Obviously, with an SQL trigger the DB has to be doing basically the same thing.

So I don't think there's two much difference between the two methods.

Charles

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Troy Foster
Sent: Thursday, August 23, 2007 1:48 PM
To: Midrange Systems Technical Discussion
Subject: Re: Triggers

your second is wrong. I check field changes all the time with
my PF triggers.

This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.

--
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.