From 2f02c77b4ef1d6a7d6a8e8862ead5592863d7988 Mon Sep 17 00:00:00 2001 From: Kevin Israel Date: Thu, 26 Sep 2013 01:38:02 -0400 Subject: [PATCH] Use utf8 charset for searchindex MySQL table This prevents the DB error "1283 Column 'si_title' cannot be part of FULLTEXT index", which happens when the "binary" charset is used. Note that 2ab7c9ec3b fixed the problem for creation of new DBs, though not for reuse of existing DBs. It is still necessary to specify the character set for the table itself. Bug: 47191 Change-Id: Ib4f30fd2730839af1323295898e6dce47b27068d --- RELEASE-NOTES-1.22 | 2 ++ maintenance/tables.sql | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/RELEASE-NOTES-1.22 b/RELEASE-NOTES-1.22 index 957ee64ff2..c9bff695ea 100644 --- a/RELEASE-NOTES-1.22 +++ b/RELEASE-NOTES-1.22 @@ -314,6 +314,8 @@ production. * (bug 6200) line breaks in
are handled like they are in
* (bug 14931) Default character set now set to 'utf8' when a new MySQL database is created. +* (bug 47191) Fixed "Column 'si_title' cannot be part of FULLTEXT index" + MySQL error when installing using the binary character set option. === API changes in 1.22 === * (bug 25553) The JSON output formatter now leaves forward slashes unescaped diff --git a/maintenance/tables.sql b/maintenance/tables.sql index df1bc06f84..d37ca47b66 100644 --- a/maintenance/tables.sql +++ b/maintenance/tables.sql @@ -1132,7 +1132,7 @@ CREATE TABLE /*_*/searchindex ( -- Munged version of body text si_text mediumtext NOT NULL -) ENGINE=MyISAM; +) ENGINE=MyISAM DEFAULT CHARSET=utf8; CREATE UNIQUE INDEX /*i*/si_page ON /*_*/searchindex (si_page); CREATE FULLTEXT INDEX /*i*/si_title ON /*_*/searchindex (si_title); -- 2.20.1