Last modified: 2013-07-30 00:10:41 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T25694, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 23694 - fail to create "searchindex" with mysql and db collation = "binary"
fail to create "searchindex" with mysql and db collation = "binary"
Status: REOPENED
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.22.0
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2010-05-28 10:46 UTC by Yuki Seaside
Modified: 2013-07-30 00:10 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Yuki Seaside 2010-05-28 10:46:39 UTC 
(...)
Database wiki exists
Creating tables... FAILED
Query "CREATE FULLTEXT INDEX si_title ON `searchindex` (si_title) " failed with error code "Column 'si_title' cannot be part of FULLTEXT index (localhost)".
Comment 1 Yuki Seaside 2010-05-28 11:01:34 UTC 
After reload the installation page, it will continue because 'searchindex' already exist, but the mainpage, default user and l10n-cache may not be created properly.
Comment 2 Max Semenik 2010-05-28 12:00:53 UTC 
Hmm, looks like we just need to set some collation for it explicitly, to prevent server defaults from interferring. latin1_swedish_ci?
Comment 3 CBM 2011-01-20 15:55:20 UTC 
The beta installer for 1.18 has hit this bug again; I see it when trying to install with r80627
Comment 4 CBM 2011-01-20 16:28:33 UTC 
I'm not sure how to interpret comment 2. Can varbinary columns have a collation at all? Changing severity to major, since this stops the installer even if 'utf8' is selected earlier.
Comment 5 Mark A. Hershberger 2011-01-20 19:50:26 UTC 
this appears to be fixed for 1.17.  Removing blocker there.
Comment 6 Chad H. 2011-01-20 20:01:17 UTC 
It's not present in REL1_17, but it is in trunk.

r80547 is to blame.
Comment 7 Chad H. 2011-01-26 15:41:52 UTC 
(In reply to comment #3)
> The beta installer for 1.18 has hit this bug again; I see it when trying to
> install with r80627

Are you still hitting this with head (r81026)? I'm pretty sure this is resolved.
Comment 8 Bartosz Dziewoński 2013-07-11 13:00:28 UTC 
This has just happened to me on git master. I changed database collation to utf8_general_ci, dropped all tables, refreshed the installer and it worked.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links