Hi!
On Jan 07, Erlend Hopso Stromsvik wrote:
> > What I can easily do without breaking 4.0.x "gamma" status, is to add
> > command line switch --disable-fulltext-stopwords. It can help as a
> > temporary solution, untill a proper fix - per-index options, that is -
> > will be implemented.
>
> Tha
> What I can easily do without breaking 4.0.x "gamma" status, is to add
> command line switch --disable-fulltext-stopwords. It can help as a
> temporary solution, untill a proper fix - per-index options, that is -
> will be implemented.
That would be helpful for me, but what about Thomas Spahni's
On Mon, 6 Jan 2003, Sergei Golubchik wrote:
> > Does the stopword list have to be 'hardcoded' in myisam/ft_static.c?
>
> No, of course, it has not.
> The problem is, that I cannot implement something like
>
>CREATE TABLE ... ( ... FULLTEXT (...) WITHOUT STOPWORD LIST )
> or
>CREATE TABLE .
Hi!
On Jan 06, Erlend Hopsø Strømsvik wrote:
>
> Hi
>
> I'm currently using MySQL (4.0.4 recompiled) as our database for storing
> information about books.
> There are about 1.5mill book titles + other information in the database now.
>
> The fulltext search capabilities of MySQL have turned ou
