[FX.php List] Record Count after the fact- Revisted

[Steve Winter]

Yip... I did consider suggesting session variables, however with the sort of
volume of data that I think Jonathan is talking about, I decided like you
Dan, that this was going to be too much overhead to handle on each page...


-----Original Message-----
From: fx.php_list-bounces at mail.iviking.org
[mailto:fx.php_list-bounces at mail.iviking.org] On Behalf Of DC
Sent: Thursday, 22 February 2007 5:21 a.m.
To: FX.php Discussion List
Subject: Re: [FX.php List] Record Count after the fact- Revisted

be careful putting too much data into SESSION vars as they are loaded on 
every page request. also, make sure you explicitly remove the data when 
you don't need it anymore so it doesn't load and slow the server.

dan

Gjermund Gusland Thorsen had written:
> And then you would only need $_SESSION['filteredResultMax'] and 
> $_SESSION['filteredResultSkip'] to display your desired data.
> 
> ggt667
> 
> On 2/21/07, * Gjermund Gusland Thorsen* <ggt667 at gmail.com 
> <mailto:ggt667 at gmail.com>> wrote:
> 
>     I would put the new filtered result in $_SESSION['filteredResults']
> 
>     ggt667
> 
> 
>     On 2/20/07, *Joel Shapiro * < jsfmp at earthlink.net
>     <mailto:jsfmp at earthlink.net>> wrote:
> 
>         Hiya Jonathan
> 
>         I had a thought from your last thread that I don't remember
>         seeing --
>         though maybe I just missed it...
> 
>         As the php goes through your FM results, can you put all your
newly
>         filtered, looped-through data into a new array and then
subsequently
>         only use that?  So that your $filteredResults array would contain
>         only the 300 'records' (of the 500 found by FM)?  Then it seems
you
>         could do whatever you wanted to that data: display the count, re-
>         sort, prev/next, etc.
> 
>         maybe?
> 
>         -Joel
> 
> 
>         On Feb 20, 2007, at 2:01 PM, Jonathan Schwartz wrote:
> 
>         >  I'm baaa-aaack...with a wrinkle in the previously discussed
issue
>         >  of post-processing a query result to accomplish a combines
AND/OR
>         >  search.
>         >
>         >  The problem now is dealing with PREV/NEXT links. I didn't
>         realize I
>         >  had a problem until this point.
>         >
>         >  The process:
>         >  1) Perform part 1 of the search with FMP. Say it returns 500
>         >  records. $searchResult[foundCount'] reports 500, but this is
>         before
>         >  the secondary search and can not be reported back to the user.
>         >
>         >  2) FMP passes 500 records back to PHP and Part 2 of the search
>         (for
>         >  loop) reduces the 500 records to say, 300. I can report this
back
>         >  to the user, but only if I set groupsize high (500) in order to
be
>         >  sure to count all the records resulting from the second step.
Set
>         >  it lower and the count could be wrong.
>         >
>         >  3) I'm ready to post the first 20 records, but I have 300.  If
I
>         >  set groupsize to 20, I get say 15.  Can't do that. If I decide
to
>         >  accept the 300 records and stop the for loop at 20 records,
that
>         >  would be wasting alot of cycles just to to toss 90% of the
data.
>         >  Plus, how do I now deal with the second 20 records with PREV
and
>         >  NEXT links?
>         >
>         >  Am I thinking about this correctly?  I've already asked the end
>         >  user if they *really* need checkboxes versus radio buttons on
>         this
>         >  search. ;-)
>         >
>         >  J
>         >
>         >
>         >  --
>         >
>         >  Jonathan Schwartz
>         >  FileMaker 8 Certified  Developer
>         >  Associate Member, FileMaker Solutions Alliance
>         >  Schwartz & Company
>         >  jonathan at eschwartz.com <mailto:jonathan at eschwartz.com>
>         >  http://www.eschwartz.com
>         >  http://www.exit445.com
>         >  415-381-1852
>         >
>         >  _______________________________________________
>         >  FX.php_List mailing list
>         >  FX.php_List at mail.iviking.org
<mailto:FX.php_List at mail.iviking.org>
>         >  http://www.iviking.org/mailman/listinfo/fx.php_list
> 
>         _______________________________________________
>         FX.php_List mailing list
>         FX.php_List at mail.iviking.org <mailto:FX.php_List at mail.iviking.org>
>         http://www.iviking.org/mailman/listinfo/fx.php_list
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
_______________________________________________
FX.php_List mailing list
FX.php_List at mail.iviking.org
http://www.iviking.org/mailman/listinfo/fx.php_list

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.441 / Virus Database: 268.18.1/690 - Release Date: 16/02/2007
2:25 p.m.
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.441 / Virus Database: 268.18.1/690 - Release Date: 16/02/2007
2:25 p.m.