On Jan 9, 2008 8:34 AM, Sebastian Mendel <[EMAIL PROTECTED]> wrote:
> yes, as written in the mentioned article the test is only relevant with
> correct used indexes, but MySQL does not use more than one index, so this
> query cannot all be done with indexes
Well, first of all, MySQL 5 does use mor
Perrin Harkins schrieb:
> On Jan 9, 2008 4:33 AM, Sebastian Mendel <[EMAIL PROTECTED]> wrote:
>> usually ... but i do not know of any index capable of having FULLTEXT and
>> 'normal' fields in one index
>
> Does that matter?
yes, as written in the mentioned article the test is only relevant with
On Jan 9, 2008 4:33 AM, Sebastian Mendel <[EMAIL PROTECTED]> wrote:
> usually ... but i do not know of any index capable of having FULLTEXT and
> 'normal' fields in one index
Does that matter? It would have to be doing a full scan for
SQL_CALC_FOUND_ROWS to work out well.
- Perrin
--
MySQL Gen
Perrin Harkins schrieb:
> On Jan 4, 2008 5:51 PM, Eben <[EMAIL PROTECTED]> wrote:
>> The resultset is paginated on the front end using the
>> SQL_CALC_FOUND_ROWS functionality...
>
> Usually a bad idea:
> http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_foun
I've never used this feature before on my application.
On Jan 5, 2008 7:06 AM, Perrin Harkins <[EMAIL PROTECTED]> wrote:
> On Jan 4, 2008 5:51 PM, Eben <[EMAIL PROTECTED]> wrote:
> > The resultset is paginated on the front end using the
> > SQL_CALC_FOUND_ROWS functionality...
>
> Usually a bad i
On Jan 4, 2008 5:51 PM, Eben <[EMAIL PROTECTED]> wrote:
> The resultset is paginated on the front end using the
> SQL_CALC_FOUND_ROWS functionality...
Usually a bad idea:
http://www.mysqlperformanceblog.com/2007/08/28/to-sql_calc_found_rows-or-not-to-sql_calc_found_rows/
- Perrin
--
MySQL Gener
I left something out, the query looks like:
SELECT SQL_CALC_FOUND_ROWS table_1.id,table_2.*
FROM table_2
LEFT JOIN table_1 ON table_2.shared_id = table_1.shared_id
WHERE MATCH table_2.field AGAINST ('value')
AND table_2.current = 1
AND table_2.shared_id IN (SELECT shared_id FROM table_1_view)
LIMI
