Miller, Terion wrote:
> Ok, say you have a database with 16000 records in it, but you only want to
> call out say 2000 records at a time as the search/query is performed, then
> store the first 2000 in a session and then retrieve the next 2000 etc etc as
> a way to minimize server strain?
> (I'm tasked to do this and ....)
> 1. don't know what this is called to google it...partioning results/data ???
> 2. Is there a better way to deal with retrieval of large amounts of data
> from a large table without choking the server.....
> 3. Is it possible at all....
> Basically I need to know what it is I'm looking to do, it's not getting
> explained in an understandable way here....which makes google useless....
> I love my job, I love my job....I love...my job...monday Monday monday
It's called a bad idea. Instead of doing one query to get your data,
you're going to do eight?
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php