Re: [PHP-DB] What is the most efficient way to store SELECT results

2007-10-12 Thread Leo G. Divinagracia III
Robert Palmer wrote: I'm not I was clear in my question. A query returns 1,000 rows from the table. I want to store the entire result of that query in order to be able to create separate pages to return the results rather than all on one page e.g. Page 1 2 3 4 ... . Not sure if it's

Re: [PHP-DB] What is the most efficient way to store SELECT results

2007-10-09 Thread [EMAIL PROTECTED]
Robert wrote: I want to store the results of a SELECT query in order to be able to page through those results and allow the user to select one, see it in more details and then return to the original list of results. What's the usual technique for doing this? place a get variable after the

Re: [PHP-DB] What is the most efficient way to store SELECT results

2007-10-09 Thread Robert Palmer
I'm not I was clear in my question. A query returns 1,000 rows from the table. I want to store the entire result of that query in order to be able to create separate pages to return the results rather than all on one page e.g. Page 1 2 3 4 ... . Not sure if it's important but I'm using

Re: [PHP-DB] What is the most efficient way to store SELECT results

2007-10-09 Thread Roberto Mansfield
Many sites just requery the database on each page and just return the relevant results. If you are using mysql, you can use LIMIT in your query to restrict the results for a specific page. You can also do something in similar in Oracle using nested queries and row ids. If the query is slow, you

[PHP-DB] What is the most efficient way to store SELECT results

2007-10-08 Thread Robert
I want to store the results of a SELECT query in order to be able to page through those results and allow the user to select one, see it in more details and then return to the original list of results. What's the usual technique for doing this? -- PHP Database Mailing List