MySQL Bugs: #3011: Fulltext with UTF8 irrelevant results (or errors)

Bug #3011	Fulltext with UTF8 irrelevant results (or errors)
Submitted:	28 Feb 2004 17:10	Modified:	29 Feb 2004 13:49
Reporter:	[ name withheld ]	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: MyISAM storage engine	Severity:	S3 (Non-critical)
Version:	4.1.1	OS:	Linux (Linux)
Assigned to:	Sergei Golubchik	CPU Architecture:	Any

Description:
When using similar words with only different accents/diacritical marks in utf8 
database, the fulltext search gives errors, bad results or at least irrelevant 
relevance values. 

How to repeat:
see attachment

example (utf8) - see mainly the 4th query, unfortunately no "storage errors -1" reproducable

Attachment: problem_example.txt (text/plain), 4.31 KiB.

could you please attach a table dump (as created by mysqldump) for these tables ?

A question: could there be a problem (it is not the only one) with having two 
TEXT columns in one common FULLTEXT index, while one of these columns can be 
NULL? 
 
P.S.: I'll try to make a better demonstration table as soon as possible, 
thanks.

an example of a complete session with errors (create database, tables, ...), UTF8 of course

Attachment: example2.txt (text/plain), 3.12 KiB.

mysqldump -u root -p test1 --default-character-set=utf8 >example2_dump.txt

Attachment: example2_dump.txt (text/plain), 1.13 KiB.

An complete (unmodified) examples session added as well as the dump of the 
table/database.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Thanks!

I fixed the bug, the fix will come with 4.1.2