[PHP] Previous & Next Navigation

2002-06-03 Thread Jay Blanchard
Howdy! I am working on a project where approximately 3k - 5k records are returned and need to be displayed 30 per page with 'previous' and 'next' navigation at the request of the users. Does anyone know of an efficient script that will do this in PHP (with MySQL) that will not query the database

Re: [PHP] Previous & Next Navigation

2002-06-03 Thread 1LT John W. Holmes
nday, June 03, 2002 1:06 PM Subject: [PHP] Previous & Next Navigation > Howdy! > > I am working on a project where approximately 3k - 5k records are returned > and need to be displayed 30 per page with 'previous' and 'next' navigation > at the request of the use

RE: [PHP] Previous & Next Navigation

2002-06-03 Thread Jay Blanchard
[snip] So you think it's more efficient and faster to load a 3 - 5 thousand row table into an array in memory and pass that around to all of your scripts (through sessions?), rather than just passing a $page variable and doing a query to return 30 rows on each page?? If you pass a $Page variable,

Re: [PHP] Previous & Next Navigation

2002-06-03 Thread 1LT John W. Holmes
do the subsequent paging out of that table (which will be faster, only having 3-5K rows). run a cron job to delete temp tables after the are X minutes old, etc... ---John Holmes... - Original Message - From: "Jay Blanchard" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> S

RE: [PHP] Previous & Next Navigation

2002-06-03 Thread Jason Soza
al Message - From: "Jay Blanchard" <[EMAIL PROTECTED]> Date: Monday, June 3, 2002 11:07 am Subject: RE: [PHP] Previous & Next Navigation > [snip] > So you think it's more efficient and faster to load a 3 - 5 > thousand row > table into an array in memory and pas

RE: [PHP] Previous & Next Navigation

2002-06-03 Thread Jay Blanchard
[snip] Okay...glad to see someone put some thought into it instead of just wanting to do it because "queries are bad!". Also, the speed of the query doesn't depend on the connection speed at all. [/snip] I know...in this case it is just the number of records that are needed vs. the number of reco

RE: [PHP] Previous & Next Navigation

2002-06-03 Thread David Freeman
> The memory footprint of the 3k - 5k of records, even if the > total memory needed for each record is 1k (which it is not), > is 30k - 50k RAM, less than the size of most web pages. The > LIMIT query, running on a slow server to simulate dial-up > connections, takes anywhere from 1.3 to

Re: [PHP] Previous & Next Navigation

2002-06-03 Thread Justin French
Only querying the database once would result in you having to set a massive session, cookie, or something to hold the whole result in. Doesn't sound right to me... for starters, 3000 records / 30 per page = 100 pages... it seems unlikely that every user will make it through the 100 pages, so they

RE: [PHP] Previous & Next Navigation

2002-06-03 Thread Martin Towell
, 2002 11:40 AM To: Jay Blanchard; [EMAIL PROTECTED] Subject: Re: [PHP] Previous & Next Navigation Only querying the database once would result in you having to set a massive session, cookie, or something to hold the whole result in. Doesn't sound right to me... for starters, 3000 rec