From: Kevin Israel <pleasestand@live.com>
Date: Thu, 26 Sep 2013 05:38:02 +0000 (-0400)
Subject: Use utf8 charset for searchindex MySQL table
X-Git-Tag: 1.31.0-rc.0~18677^2
X-Git-Url: https://git.cyclocoop.org/%27.%24link.%27?a=commitdiff_plain;h=2f02c77b4ef1d6a7d6a8e8862ead5592863d7988;p=lhc%2Fweb%2Fwiklou.git

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
---

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 <blockquote> are handled like they are in <div>
 * (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);