Re: C api mysql_store_result vs mysql_use_result

2012-02-09 Thread Johan De Meersman
- Original Message - > From: "Alex Schaft" > > 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-bas

Re: C api mysql_store_result vs mysql_use_result

2012-02-09 Thread Alex Schaft
On 2012/02/09 01:40 PM, Johan De Meersman wrote: - Original Message - From: "Alex Schaft" If I were to do a select count(*) from x where y prior to doing select * from x where y to get a number of records, how would this impact performance on the server itself? Would the first query be

Re: C api mysql_store_result vs mysql_use_result

2012-02-09 Thread Johan De Meersman
- Original Message - > From: "Alex Schaft" > > If I were to do a select count(*) from x where y prior to doing > select * from x where y to get a number of records, how would this impact > performance on the server itself? Would the first query be the one to > do the most processing, with

C api mysql_store_result vs mysql_use_result

2012-02-08 Thread Alex Schaft
Hi, I'm currently using mysql_store_result to retrieve all records of a query. This poses a problem however if say a couple of thousand records get returned, and the user gets no feedback during the progress. I now want to change this to mysql_use_result. The only catch is that you don't know