----- Original Message ----- > From: "Alex Schaft" <al...@quicksoftware.co.za> > > From the user's perspective, they just need to know the process didn't > hang. The count() query is more for getting memory requirements upfront. > Can I handle it all, or do I need to break it down into pages?
Then just use the cursor-based api (I guess that's mysql_use_result) all the time, and you won't have any memory problems at all. If you need to retrieve pages (as in, the third block of 10 results, for instance) LIMIT is your friend. Do read the documentation on limit, though - there's performance caveats when you use order by and similar. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
