× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I've been trying to work out the difference between triggers implemented
via SQL and triggers implemented through the ADDPFTRG command.

 

I've been using both types, but haven't been ale to find any
documentation on which was one is more appropriate in particular
circumstances.

 

I often use SQL triggers to trap obscure bugs which place erroneous data
in the data base. I found some code some time ago which enabled me to
trap the data condition in the SQL trigger code and pass a bunch of
values to an SQL procedure which then invoked a CL program and passing
it values obtained from the 'new row' row.

 

I've also recently added a trigger via ADDPFTRG to trigger the
generation of an e-mail when a record was inserted into a file. This
trigger simply invokes the CL program but doesn't pass any values across
because ADDPFTRG doesn't allow this. From other reading it appears that
a trigger buffer is available to obtain information in lieu of
parameters. It appear that an RPG trigger program would be best in this
circumstance.

 

I'm trying to make sense of all the options available and was wondering
if there is a simple article which covers the issues I've raised above.

 

Thanks again.


*********************************************************************************************************
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you are not the intended recipient, any use, disclosure or copying of this 
message is unauthorised. If you have received this message in error, please 
reply using the sender's email address. 

This footnote confirms that this email message has been scanned for computer 
viruses. EIG-Ansvar Limited does not accept liability for any loss or damage, 
whether caused by our own negligence or not, that results from a computer virus 
or defect in the transmission of this email or any attached file. 

EIG-Ansvar Limited - Australia (A.B.N. 21 007 216 506)
Email : insure@xxxxxxxxxxxxxxxx

Eig-Ansvar Limited - New Zealand
Email : insure@xxxxxxxxxxxxxxxx

*********************************************************************************************************

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.