Re: a need for speed

pehaps a nice way for the trigger solution will be to say :

one modification (delete, insert,  change) for partial key A, B, C then run
a little PGm that will partial manage the summary file (delete for key and
rebuil for this key)


----- Original Message ----- 
From: "Douglas Handy" <dhandy@xxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Friday, August 19, 2005 5:22 PM
Subject: Re: a need for speed


> Rob et al,
>
> > Or instead of modifying the program(s) that maintain the detail file,
put
> > a trigger on the detail file to maintain the summary.
>
> Having a trigger (or modifying the other programs which modify the
> detail file) may be the optimum solution if all that occurs are record
> inserts.  But what should a delete trigger do when if finds the detail
> record being deleted happens to match a current value in the summary
> file?  You don't know what new value to place in the summary file
> (assuming the detail file is unordered and there is no relevant LF
> access path).
>
> A record update of one of the relevant fields could also if the fields
> values in the "was" buffer match a summary record instance.
>
> However, if only record insertions occur, then my vote is for a
> trigger on the detail files which either directly maintains the
> summary file or puts entries to a DTAQ to defer that task to another
> job.
>
> Doug
>
> -- 
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>