As per select * from indexed_table where match(indexed_col)
against ('+oracle +sybase +london -oracle')
> > Nothing was returned.
>
> What did you expect ? This query should return only rows that
> contain the word "oracle" AND did not contain it at the same time.
I expected it to return just reformat the query to:
select * from indexed_table where match(indexed_col)
against ('+sybase +london -oracle')
Apart from that point taken.
I have just done this:
select * from indexed_table where match(indexed_col)
against ('"visual basic"')
This returns rows with either visual or basic. I read
phrase searching was allowed in mySQL v4.0?
*********************************************************************
* Visit http://www.computerstaff.net - Computer Jobs at all LEVELS *
*********************************************************************
> -----Original Message-----
> From: Sergei Golubchik [mailto:[EMAIL PROTECTED]]
> Sent: 20 May 2001 20:51
> To: technical Support
> Subject: Re: Fulltext Strange Results...
>
>
> Hi!
>
> On May 20, technical Support wrote:
> > Hello,
> >
> > I did the following query against my indexed table:
> >
> > select * from indexed_table where match(indexed_col)
> > against ('oracle +sybase +london')
> >
> > It returned 16 rows of which only 4 rows included all words.
>
> Sure thing. You didn't specify that the word
> "oracle" MUST be present in all the rows returned.
>
> > I then did:
> >
> > select * from indexed_table where match(indexed_col)
> > against ('+oracle +sybase +london')
> >
> > It returned 4 rows which is the desired or expected results.
>
> That's correct.
>
> > I then did:
> >
> > select * from indexed_table where match(indexed_col)
> > against ('+oracle +sybase +london -oracle')
> >
> > Nothing was returned.
>
> What did you expect ? This query should return only rows that
> contain the word "oracle" AND did not contain it at the same time.
>
> > I then went on to do this:
> >
> > select * from indexed_table where match(indexed_col)
> > against ('oracle and sybase and london')
> >
> > This returned over 200 rows rather than the expected 4.
>
> AND is not a proper boolean operator in fulltext search as of MySQL-4.0
>
> >
> > This was done against mySQL v4.0.
> >
> > Can someone please explain the ambiguities.
>
> No ambiguities - all the results are as expected.
>
> Regards,
> Sergei
>
> --
> MySQL Development Team
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Sergei Golubchik <[EMAIL PROTECTED]>
> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/
> /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany
> <___/
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
