At 05:17 PM 8/28/2003, you wrote:
Hi,
no - adding a limit doesn't really help.
thanks,
- Mark
Mark et al,
Has anyone tried MNOGoSearch (http://search.mnogo.ru/) as a full
text replacement for MySQL? Although it 's primary focus is to index web
pages, it can also be used directly on MySQ
Hello
If You need some elp You have to give us more details:
What version You use?
Does exist one fulltext index on title + keywords?
The schema and indexes.
The result of:
explain select count(*) from resources where match title,keywords
against('common word');
I think index file size is small.
Hi,
no - adding a limit doesn't really help.
thanks,
- Mark
On Thu, 28 Aug 2003 16:12:41 -0400, John Larsen wrote:
>Mark wrote:
>Why don't you just always put a limit 1000 on it, do you ever need
>more
>than that?
>
>>Hi,
>>I have a fulltext index on a table with 80,000 rows. when I do a
>>search
Because his query only returns one record. A limit wouldn't make any
difference.
John Larsen wrote:
Mark wrote:
Why don't you just always put a limit 1000 on it, do you ever need
more than that?
Hi,
I have a fulltext index on a table with 80,000 rows. when I do a
search for a common word it i
Mark wrote:
Why don't you just always put a limit 1000 on it, do you ever need more
than that?
Hi,
I have a fulltext index on a table with 80,000 rows. when I do a
search for a common word it is very slow, for example:
select count(*) from resources where match title,keywords
against('common w
Hi,
I have a fulltext index on a table with 80,000 rows. when I do a
search for a common word it is very slow, for example:
select count(*) from resources where match title,keywords
against('common word');
might take over a minute if there are a 5,000 or so rows that match.
I'm looking for a way
