| Bug #2330 | fulltext search with gb2312/gbk failed | ||
|---|---|---|---|
| Submitted: | 8 Jan 2004 18:05 | Modified: | 8 Jan 2004 23:40 |
| Reporter: | Yongzhong Xie | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server: MyISAM storage engine | Severity: | S2 (Serious) |
| Version: | 4.1.1 | OS: | Linux (linux) |
| Assigned to: | CPU Architecture: | Any | |
[8 Jan 2004 23:40]
Sergei Golubchik
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.mysql.com/documentation/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Additional info: crash is already fixed - as you found. "no results returned" - is the expected behaviour, see the manual about 50% threshold. http://www.mysql.com/doc/en/Fulltext_Search.html

Description: MySQL manual descript: Full-text search now supports multi-byte character sets and the Unicode utf8 character set. But when I create a gb2312 or gbk table and do a full-text search no result return. test with 4.1.1 -- mysql crashed and no respones test with last snapshot 4.1.2 -- no result return. How to repeat: CREATE TABLE `gb2312test` ( `t` TEXT CHARACTER SET gb2312 NOT NULL , FULLTEXT ( `t` ) ) CHARACTER SET = gb2312; INSERT INTO `gb2312test` VALUES ('È«ÎÄËÑË÷ÖÐÎIJâÊÔ, fulltext test'); INSERT INTO `gb2312test` VALUES ('È«ÎÄËÑË÷ÖÐÎIJâÊÔ, fulltext test'); INSERT INTO `gb2312test` VALUES ('È«ÎÄËÑË÷ÖÐÎIJâÊÔ, fulltext test'); INSERT INTO `gb2312test` VALUES ('È«ÎÄËÑË÷ÖÐÎIJâÊÔ, fulltext test'); INSERT INTO `gb2312test` VALUES ('È«ÎÄËÑË÷ÖÐÎIJâÊÔ, fulltext test'); INSERT INTO `gb2312test` VALUES ('È«ÎÄËÑË÷ÖÐÎIJâÊÔ, fulltext test'); SELECT * FROM `gb2312test` WHERE MATCH t AGAINST ( "fulltext" ) ; SELECT * FROM `gb2312test` WHERE MATCH t AGAINST ( "ÖÐÎIJâÊÔ" )