managing large result sets
| From: | houston | Date: | Wed, 28 Mar 2001 18:14:51 +0000 |
| Subject: | managing large result sets | ||
| Groups: | php.db | ||
| Request: | Send a blank email to php-db+get-7941@lists.php.net to get a copy of this message | ||
I have to deal with displaying result sets that could potentially be quite
large. It would be bad form to drop 10,000 rows into a browser table so I
need a strategy for dealing with this possibility.
It's obviously not a big deal to limit the output but what is the typical
strategy for handling <next> <previous> behavior? It seems terribly
inefficient to requery for a subset each time. I suppose that I could dump
the entire result set to a text file keyed to the session but that raises
the problem of garbage collection with potentially large files. Anyone have
experience with this problem?
Thanks--Houston