|
From: Charles Wilt <charles.wilt@xxxxxxxxx>message?
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 06/01/2010 08:58 AM
Subject: Re: Compiling after file changes
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Yes, it could result in lots of _logical_ reads, since the page should
be in memory after the first read. But logical reads aren't nearly as
costly as physical ones.
Your service program could also check to see if it's already got the
data for the custom on-hand before reading it again.
You'd call other getters for the additional information you'd need for
the message.
If you find out that you often need the same group of fields, then you
could build a single getter that returns a DS (whose structure doesn't
change ;)
Charles
On Mon, May 31, 2010 at 3:49 AM, David FOXWELL
<David.FOXWELL@xxxxxxxxx> wrote:
customer? What if I other customer information must be used in the-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Charles Wilt
DO NOT SIMPLY CREATE GETTERS/SETTERS FOR EVERY FIELD!
Instead, have business logic routines that you can call.
Do this:
if CUSTOMER_IsOverCreditLimit(wCustomerNumber:wSaleAmount);
//display message?
endif;
Instead of this:
if wSaleAmount > CUSTOMER_GetCreditLimit(wCustomerNumber);
//display message?
endif;
Isn't that going to result in a load of file reads for the same
list--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
As an Amazon Associate we earn from qualifying purchases.
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.