diff options
| author | svoj@may.pils.ru <> | 2006-05-29 16:46:46 +0500 |
|---|---|---|
| committer | svoj@may.pils.ru <> | 2006-05-29 16:46:46 +0500 |
| commit | 53279f1dc487a70d2223b63550af9fd633510945 (patch) | |
| tree | 2d99880d147ef4ce559982554840a1011fb091e9 /mysql-test/r/fulltext2.result | |
| parent | 7f6afa8b2a0d1c66b169bc58f8db24298f0d8364 (diff) | |
| download | mariadb-git-53279f1dc487a70d2223b63550af9fd633510945.tar.gz | |
BUG#19580 - FULLTEXT search produces wrong results on UTF-8 columns
The problem was that MySQL hadn't true ctype implementation. As a
result many multibyte punctuation/whitespace characters were
treated as word characters.
This fix uses recently added CTYPE table for unicode character sets
(WL1386) to detect unicode punctuation/whitespace characters
correctly.
Note: this is incompatible change since it changes parser behavior.
One will have to use REPAIR TABLE statement to rebuild fulltext
indexes.
Diffstat (limited to 'mysql-test/r/fulltext2.result')
| -rw-r--r-- | mysql-test/r/fulltext2.result | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/mysql-test/r/fulltext2.result b/mysql-test/r/fulltext2.result index f6a4b20bc22..7e3e25370d3 100644 --- a/mysql-test/r/fulltext2.result +++ b/mysql-test/r/fulltext2.result @@ -241,3 +241,11 @@ select * from t1 where match a against('ab c' in boolean mode); a drop table t1; set names latin1; +SET NAMES utf8; +CREATE TABLE t1(a VARCHAR(255), FULLTEXT(a)) ENGINE=MyISAM DEFAULT CHARSET=utf8; +INSERT INTO t1 VALUES('„MySQL“'); +SELECT a FROM t1 WHERE MATCH a AGAINST('“MySQL„' IN BOOLEAN MODE); +a +„MySQL“ +DROP TABLE t1; +SET NAMES latin1; |