Re: Using PF constraints

Booth,

If all you want is a simple cascaded delete then use the constraint.  ZERO 
lines of programming has to be a productivity enhancement versus a 
trigger.  And, if you have other children, and/or other generations, then 
it is all done automatically.

I am not knocking triggers.  I use them all the time.  Just a matter of 
using the right tool for the job.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Booth Martin" <Booth@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/29/2003 11:19 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     <midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: Using PF constraints


Time for me to learn again. 



Why would a constraint be preferable to a trigger?   Or would you use 
both,
with the constraint triggering other events on other related files?



 

---------------------------------------------------------

Booth Martin   http://www.MartinVT.com

Booth@xxxxxxxxxxxx

---------------------------------------------------------

 

-------Original Message-------

 

From: Midrange Systems Technical Discussion

Date: Tuesday, April 29, 2003 09:45:15

To: 'midrange-l@xxxxxxxxxxxx'

Subject: Using PF constraints

 

Hello all,

 

I am canvassing for opinions on using ADDPFCST to effect data purges 
instead

of writing (comparatively) more complex RPG programs to perform this

function. The way I see it, if we add the appropriate constraint to a

detail file which has an associated header file with a primary key and

specify 'cascading delete', deleting records from the header file will

automatically zap the associated detail records right?

 

Is there a good reason why I've never seen this being used? Or is it just

the shops that I've worked with that do not think this is a useful 
feature?

 

Thanks in advance for your opinions.

 

 

Martin

 

 

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

" This message contains information that may be privileged or confidential
and 

is the property of the Cap Gemini Ernst & Young Group. It is intended only
for 

the person to whom it is addressed. If you are not the intended recipient,
you 

are not authorized to read, print, retain, copy, disseminate, distribute, 
or
use 

this message or any part thereof. If you receive this message in error,
please 

notify the sender immediately and delete all copies of this message ".

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

 

_______________________________________________

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

 

. _______________________________________________
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.cgi/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.