Re: FULL Text Limitation issue!

2003-09-25 Thread Imran Aziz
Thank you very much Paul and Keith for your response , I guess I will have
to use LIKE clause in SQL statement for searching the records then.
Imran
- Original Message - 
From: Keith C. Ivey [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Imran Aziz [EMAIL PROTECTED]
Sent: Tuesday, September 23, 2003 5:36 PM
Subject: Re: FULL Text Limitation issue!


 On 23 Sep 2003 at 17:07, Imran Aziz wrote:
 
  I have come to know that mySQL FULL TEXT search has the limitation
  of the search phrase to be more then 3 charators. In order to
  alter the default behavior one has to alter the variable
  ft_min_word_len. I am running MySQL 3.23.54 and the FULL Text
  search works fine , but I am unable to alter the variable
  ft_min_word_len either using the my.cnf file or by altering the
  variable value on mysql startup.
 
 The ft_min_word_len variable wasn't introduced until MySQL 4.  See 
 http://www.mysql.com/doc/en/Fulltext_Fine-tuning.html
 
 -- 
 Keith C. Ivey [EMAIL PROTECTED]
 Tobacco Documents Online
 http://tobaccodocuments.org
 
 


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



FULL Text Limitation issue!

2003-09-23 Thread Imran Aziz
Hello All,
I have come to know that mySQL FULL TEXT search has the limitation of the search 
phrase to be more then 3 charators. In order to alter the default behavior one has to 
alter the variable ft_min_word_len. 
I am running MySQL 3.23.54 and the FULL Text search works fine , but I am unable 
to alter the variable ft_min_word_len either using the my.cnf file or by altering the 
variable value on mysql startup. In addition when I show all variables used by mySQL 
the variables with ft_ prefix do not show up. 
Is this FULL Text alteration limited to later verison of mySQL Server or am I 
doing something wrong , can anyone please help me with this and let me know how to 
alter the limit of the input phrase for FULL TEXT search.
Imran.

Re: FULL Text Limitation issue!

2003-09-23 Thread Keith C. Ivey
On 23 Sep 2003 at 17:07, Imran Aziz wrote:

 I have come to know that mySQL FULL TEXT search has the limitation
 of the search phrase to be more then 3 charators. In order to
 alter the default behavior one has to alter the variable
 ft_min_word_len. I am running MySQL 3.23.54 and the FULL Text
 search works fine , but I am unable to alter the variable
 ft_min_word_len either using the my.cnf file or by altering the
 variable value on mysql startup.

The ft_min_word_len variable wasn't introduced until MySQL 4.  See 
http://www.mysql.com/doc/en/Fulltext_Fine-tuning.html

-- 
Keith C. Ivey [EMAIL PROTECTED]
Tobacco Documents Online
http://tobaccodocuments.org


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: FULL Text Limitation issue!

2003-09-23 Thread Paul DuBois
At 17:07 +0100 9/23/03, Imran Aziz wrote:
Hello All,
I have come to know that mySQL FULL TEXT search has the 
limitation of the search phrase to be more then 3 charators. In 
order to alter the default behavior one has to alter the variable 
ft_min_word_len.
I am running MySQL 3.23.54 and the FULL Text search works fine , 
but I am unable to alter the variable ft_min_word_len either using 
the my.cnf file or by altering the variable value on mysql startup. 
In addition when I show all variables used by mySQL the variables 
with ft_ prefix do not show up.
Is this FULL Text alteration limited to later verison of mySQL 
Server or am I doing something wrong , can anyone please help me 
with this and let me know how to alter the limit of the input phrase 
for FULL TEXT search.
Imran.
Yes, this variable can be set as of MySQL 4, but not in 3.23.  See:

http://www.mysql.com/doc/en/Fulltext_Fine-tuning.html

--
Paul DuBois, Senior Technical Writer
Madison, Wisconsin, USA
MySQL AB, www.mysql.com
Are you MySQL certified?  http://www.mysql.com/certification/

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Re: Full text limitation?

2003-01-10 Thread Sergei Golubchik
Hi!

  SELECT count(a.rsori) pippo
  FROM ecoras a, ecotxt b
  WHERE MATCH ( b.rstxt ) AGAINST ( '-linux' IN BOOLEAN MODE )
  AND a.rsori = b.rsori
  AND a.rscod = b.rscod;
  
 If I execute a query like in the example, I don't obtain all rows where this
 word is not present. Instead if I use a leading plus sign I obtain the right
 resultset.
 I do not think it is a bug, maybe it is a limitation in full-text search and
 I would know how can I obtain a valid resultset.

It's not a bug, it's how fulltext search was designed to work.
`-word' works as a filter, removing rows from result set.  `+word'
and `word' add rows to result set. Naturally, if there is neither
`+word' nor `word', the result set is empty, and `-word' is useless.
 
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




Re: Full text limitation?

2003-01-09 Thread Walter Procopio
- Original Message -
From: Paul DuBois [EMAIL PROTECTED]
To: Walter Procopio [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Wednesday, January 08, 2003 5:44 PM
Subject: Re: Full text limitation?


 At 14:03 +0100 1/8/03, Walter Procopio wrote:
 Hi,
 
 I have installed mysql max 4.0.7 gamma on a Suse (ver. 8.0 professional)
 linux server. I have tried many full text queries and I had only a
problem
 with a query like this:
 
 SELECT count(a.rsori) pippo
 FROM ecoras a, ecotxt b
 WHERE MATCH ( b.rstxt ) AGAINST ( '-linux' IN BOOLEAN MODE )
 AND a.rsori = b.rsori
 AND a.rscod = b.rscod;
 
 If I use only the minus operator I have not a valid resultset.

 Isn't that the same as asking for records that don't match anything?



I think I was not exaustive, in mysql handbook I can read:


+A leading plus sign indicates that this word must be present in every
row returned.

- A leading minus sign indicates that this word must not be present in
any row returned.
  By default (when neither plus nor minus is specified) the word is
optional, but the rows that contain it will be rated higher.
  This mimicks the behaviour of MATCH() ... AGAINST() without the IN
BOOLEAN MODE modifier.

If I execute a query like in the example, I don't obtain all rows where this
word is not present. Instead if I use a leading plus sign I obtain the right
resultset.
I do not think it is a bug, maybe it is a limitation in full-text search and
I would know how can I obtain a valid resultset.


   If I use the
 minus operator with another one I have a reultset.
 For example:
 
 SELECT count(a.rsori) pippo
 FROM ecoras a, ecotxt b
 WHERE MATCH ( b.rstxt ) AGAINST ( '+linux -windows' IN BOOLEAN MODE )
 AND a.rsori = b.rsori
 AND a.rscod = b.rscod;
 
 Is it a full text limit?
 
 Thanks
 Walter Procopio



-
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




Full text limitation?

2003-01-08 Thread Walter Procopio
Hi,

I have installed mysql max 4.0.7 gamma on a Suse (ver. 8.0 professional)
linux server. I have tried many full text queries and I had only a problem
with a query like this:

SELECT count(a.rsori) pippo
FROM ecoras a, ecotxt b
WHERE MATCH ( b.rstxt ) AGAINST ( '-linux' IN BOOLEAN MODE )
AND a.rsori = b.rsori
AND a.rscod = b.rscod;

If I use only the minus operator I have not a valid resultset. If I use the
minus operator with another one I have a reultset.
For example:

SELECT count(a.rsori) pippo
FROM ecoras a, ecotxt b
WHERE MATCH ( b.rstxt ) AGAINST ( '+linux -windows' IN BOOLEAN MODE )
AND a.rsori = b.rsori
AND a.rscod = b.rscod;

Is it a full text limit?

Thanks
Walter Procopio


-
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




Re: Full text limitation?

2003-01-08 Thread Paul DuBois
At 14:03 +0100 1/8/03, Walter Procopio wrote:

Hi,

I have installed mysql max 4.0.7 gamma on a Suse (ver. 8.0 professional)
linux server. I have tried many full text queries and I had only a problem
with a query like this:

SELECT count(a.rsori) pippo
FROM ecoras a, ecotxt b
WHERE MATCH ( b.rstxt ) AGAINST ( '-linux' IN BOOLEAN MODE )
AND a.rsori = b.rsori
AND a.rscod = b.rscod;

If I use only the minus operator I have not a valid resultset.


Isn't that the same as asking for records that don't match anything?


 If I use the
minus operator with another one I have a reultset.
For example:

SELECT count(a.rsori) pippo
FROM ecoras a, ecotxt b
WHERE MATCH ( b.rstxt ) AGAINST ( '+linux -windows' IN BOOLEAN MODE )
AND a.rsori = b.rsori
AND a.rscod = b.rscod;

Is it a full text limit?

Thanks
Walter Procopio



-
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