[SPAM-5.7]- [FX.php List] Limiting fields returned

[Carl Anderson]

Dan:

Thanks for posting that.  Sadly, the PHP is perhaps 1% or less of the
overall processing time--the rest is all the data pull.

In any case, I'll look into the array_sum() function.

-- 
Carl Anderson 
Technical Support Analyst
Distance Learning 
Herberger College of the Arts
Arizona State University
http://herbergeronline.asu.edu


> From: DC <dan.cynosure at dbmscan.com>
> Reply-To: "FX.php Discussion List" <fx.php_list at mail.iviking.org>
> Date: Thu, 15 Nov 2007 13:52:50 -0500
> To: "FX.php Discussion List" <fx.php_list at mail.iviking.org>
> Subject: Re: [SPAM-5.7]- [FX.php List] Limiting fields returned
> 
> BTW, your averaging "loop" as described sounds inefficient.
> have you heard of the function array_sum()?
> 
> // this code is a sketch, you have to check for zero count
> // or risk a PHP error
> $avg = array_sum($array) / count($array);
> 
> there is usually always a better way to do things in PHP. it's a
> learning process.
> 
> also, take any unstored calculated fields off the layout if you can or
> make them stored - if they are unstored or sums or any kind of summary
> your performance will suffer greatly.
> 
> dan
> 
> Carl Anderson had written:
>> Alex:
>> 
>> While we'd love to do that, it'd require a major change in how we operate.
>> That said, my colleague and I are talking about doing so as a stop-gap
>> measure; a "whiteboard" layout is our ultimate goal, where we put
>> non-related fields that we can query easily.
>> 
>> It's too bad I can't limit what we get back.
>> 
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list