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?


PHP Database Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to