Hello,
> > Could one not store the total while using the
> index
> > and use "select FOUND_ROWS()" without
> > SQL_CALC_FOUND_ROWS to retrieve the total?
>
> Yes, it could.
> It is the optimization that wasn't implemented yet.
> (but it's in the TODO)
Once again, thanks for the response.
Could
Hi!
On Dec 05, tk wrote:
> Hello Sergei, Gunnar, and others,
>
> thank you for your quick responses.
> One little mystery remains:
>
> Why does one need to read all the row data (with
> SQL_CALC_FOUND_ROWS) to get the total number of
> results when using a limit?
>
> When the index is used to
Hello Sergei, Gunnar, and others,
thank you for your quick responses.
One little mystery remains:
Why does one need to read all the row data (with
SQL_CALC_FOUND_ROWS) to get the total number of
results when using a limit?
When the index is used to find relevant rows and sort
the results, the c
TECTED] [mailto:[EMAIL PROTECTED]
> Sent: Donnerstag, 4. Dezember 2003 16:13
> To: [EMAIL PROTECTED]
> Subject: fulltext search speed issue with SQL_CALC_FOUND_ROWS
>
>
> I have some_table with 100,000 rows and with an
> average of 500 words in some_column of each row. When
Hi!
On Dec 04, tk wrote:
> Hello,
>
> Thanks for the response.
> There is one thing that is not clear however.
>
> Regardless of whether or not I perform the fulltext
> search with or without the SQL_CALC_FOUND_ROWS
> keyword, the results that I get are exactly the same.
>
> Also, the notion
ns any faster. :-)
>
>
> Hope that helps.
>
>
> Matt
>
>
> - Original Message -
> From: <[EMAIL PROTECTED]>
> Sent: Thursday, December 04, 2003 9:13 AM
> Subject: fulltext search speed issue with
> SQL_CALC_FOUND_ROWS
>
>
> >
You might want to try your fulltext search IN BOOLEAN MODE to see if
that runs any faster. :-)
Hope that helps.
Matt
- Original Message -
From: <[EMAIL PROTECTED]>
Sent: Thursday, December 04, 2003 9:13 AM
Subject: fulltext search speed issue with SQL_CALC_FOUND_ROWS
> I h
I have some_table with 100,000 rows and with an
average of 500 words in some_column of each row. When
i do a fulltext search on this table using a query
such as the following, all of my results are under 0.1
seconds:
SELECT something
FROM some_table
WHERE MATCH (some_column) AGAINST ('some_search_
