On Fri, 13 Feb 2004, Robert Twitty wrote:
> If you are not opearating in a stateless environment, then you could use a
> cursor. The web is a stateless environment, and therefore the record set
> needs to be cached either to disk or memeory. The other alternative is to
> rerun the query for each
: Robert Twitty [mailto:[EMAIL PROTECTED]
Sent: Friday, February 13, 2004 1:59 PM
To: Paul Miller
Cc: [EMAIL PROTECTED]
Subject: RE: [PHP-DB] Paging large recordsets
If you are not opearating in a stateless environment, then you could use
a cursor. The web is a stateless environment, and therefore the
t; - Paul
>
> -Original Message-
> From: Robert Twitty [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 13, 2004 12:34 PM
> To: Karen Resplendo
> Cc: [EMAIL PROTECTED]
> Subject: Re: [PHP-DB] Paging large recordsets
>
>
> Most of the PHP solutions I have s
ltsperpage'].",
".($conf['maxresultsperpage']*$_REQUEST['page'])-10);
// loop through array returned from mysql
echo "Next";
I think. It might need some tweaking, but you get the idea (I hope).
No need to store variables here.
Beckman
>
should not store large amounts of data would be disk
write/read speed per user.
Can someone clarify this for me?
- Paul
-Original Message-
From: Robert Twitty [mailto:[EMAIL PROTECTED]
Sent: Friday, February 13, 2004 12:34 PM
To: Karen Resplendo
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DB
t; To: Karen Resplendo
> Cc: [EMAIL PROTECTED]
> Subject: Re: [PHP-DB] Paging large recordsets
>
>
> Most of the PHP solutions I have seeen require the use of session
> variables. You could create an array containing only the unique
> identifiers of all the records, and then st
Most of the PHP solutions I have seeen require the use of session
variables. You could create an array containing only the unique
identifiers of all the records, and then store it into a session variable.
You would then use another session variable to retain the page size, and
then include the pag
On Fri, 13 Feb 2004, Karen Resplendo wrote:
> I guess the time has come that my boss wants "Next", "Previous", "First",
> "Last" paging for our data displays of large recordsets or datasets.
First, do a query to find out how many rows.
select count(*) from table where (your where clauses for t