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

[Jonathan Schwartz]

Joel,

The thread was from back on Friday, where I posed the original 
question about how to accomplish a combination query.  Everyone 
agreed, I believe, that php should post-process the original found 
set.  There were two choices for what to do with the results of the 
data.  One suggestion was to create and write the resulting HTML with 
data to a variable, grab a total and then write the HTML out to the 
browser.  The other suggestion was to collect the 2nd data results in 
an array.  I went with the first approach, but now see the benefit to 
the second approach.

A couple of questions:

- Does the 300 record data array have to travel to the browser, or 
does it stay on the server.  I hope its the latter.

- The first query runs on FMP.  All subsequent PREV/NEXT links run on 
the array, right?

- What would the code look like?  There is the initial creation and 
populating of the array as the for loop progresses.   Then there are 
the "PRE/NEXT" "searches" which are more like data extractions from 
the array with given start and stop points based on groupsize.

Yikes!

J


At 2:17 PM -0800 2/20/07, Joel Shapiro 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
>>http://www.eschwartz.com
>>http://www.exit445.com
>>415-381-1852
>>
>>_______________________________________________
>>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


-- 

Jonathan Schwartz
FileMaker 8 Certified  Developer
Associate Member, FileMaker Solutions Alliance
Schwartz & Company
jonathan at eschwartz.com
http://www.eschwartz.com
http://www.exit445.com
415-381-1852