Bureaucrats, emailconfirmed, Administrators
436
edits
Changes
what to edit
The obvious solution to this is to encode your tables in a different encoding. But what if you want to still use UTF8? There is a solution.
As of 1.7.1, there are two tables affected by this problem: '''categorylinks''' and '''jobs''' (The key is 2 * (255 + 255 +8) = 1032). Both of these changes need to be made in '''/maintenance/tables.sql''' ''before'' running the initial configuration.
In categorylinks, you need to change the following line:
to
KEY cl_sortkey(cl_to(253),cl_sortkey),
To find the line, open the file in your favorite text editor, and search for '''/cat'''. Scroll down until you see the original line as shown above.
In jobs, you need to change
to
KEY (job_cmd(166), job_namespace, job_title(166))
To find the line, search for '''/jobs'''. Scroll down until you see the original line as shown above.
This guarantees that they keys are short enough so that the install won't bail.
==References==