Bug #4947 Problem with Fulltext index and utf8 in MySQL 5.0.0-alpha-standard
Submitted: 9 Aug 2004 11:19 Modified: 9 Aug 2004 18:47
Reporter: alireza vahedi Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: MyISAM storage engine Severity:S1 (Critical)
Version:5.0.0-alpha-standard OS:Microsoft Windows (win 2000, linux redhat 7.2)
Assigned to: CPU Architecture:Any

[9 Aug 2004 11:19] alireza vahedi
Description:
I have a database with 10 tables.
some of tables include english data & some of them include persian data(character set utf8).
i set utf8 to my default character set in my.cnf file.
i don't no problem with that, but when i try to use fulltext index on my tables, the mysql crashed.
i change my latin table character set to latin1 and correct this problem about latin tables.
but my persian data include latin data, adn i cannot change character set from utf8 to latin1.
in mysql logfile i see the following message very much:
Unknown character set: 'latin1_swedish_ci'

please help me

How to repeat:
I have a database with 10 tables.
some of tables include english data & some of them include persian data(character set utf8).
i set utf8 to my default character set in my.cnf file.
i don't no problem with that, but when i try to use fulltext index on my tables, the mysql crashed.
i change my latin table character set to latin1 and correct this problem about latin tables.
but my persian data include latin data, adn i cannot change character set from utf8 to latin1.
in mysql logfile i see the following message very much:
Unknown character set: 'latin1_swedish_ci'

please help me
[9 Aug 2004 18:45] Sergei Golubchik
Thank you for taking the time to report a problem.  Unfortunately
you are not using a current version of the product your reported a
problem with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions,
please change the version on this bug report to the version you
tested and change the status back to "Open".  Again, thank you for
your continued support of MySQL.
[9 Aug 2004 18:47] Sergei Golubchik
try 5.0.1 please. feel free to reopen the bugreport if you will still see that problem