Posted by cluthz on 06/17/07 12:33

"cluthz" <WHATEEVVEERR@by.co.uk> wrote in message news:TMPbi.4333>>
>> Take a look at:
>> http://dev.mysql.com/doc/refman/5.0/en/information-functions.html#function_found-rows
>
> Ahh, looks perfect. Thank you!

Actually on looking a bit more into this it seems the method described has
some bugs with it that do not actually make it faster in many cases then
running the query twice.

I found the following postings on the subject:
http://bugs.mysql.com/bug.php?id=19553

and
http://bugs.mysql.com/bug.php?id=18454

I did not fully understand the bug process yet, but it seems to me the bug
is still open and the text has made me question whether I bother changing my
code to use something which may slow down my results, especially as I'm a
bit pressured for time and don't have the luxury of benchmarking etc.

Thanks for any more input.

• Next in forum: Re: Large query results - Limiting the data, but still knowing the full row count - How?
• Prev in forum: Re: Capturing form input
• Thread view: Re: Large query results - Limiting the data, but still knowing the full row count - How?

[Reply to this message]