Difference between revisions of "lensowiki:Installation caveats"
(+refs) |
|||
| Line 17: | Line 17: | ||
Where you need to change this, I'll put up in a second. | Where you need to change this, I'll put up in a second. | ||
| + | |||
| + | ==References== | ||
| + | These bugs are actually filed on the MediaWiki bugzilla. See | ||
| + | *http://bugzilla.wikimedia.org/show_bug.cgi?id=4445 | ||
| + | *http://bugzilla.wikimedia.org/show_bug.cgi?id=1322 | ||
Revision as of 05:08, 19 July 2006
The current MediaWiki install, 1.7.1 · 2006-07-08, will run into two problems upon trying to initialize all the initial MySQL tables if those tables are encoded in UTF8. The reason this happens is that KEY fields are limited to 1000 bytes, and each character takes up 3 bytes in UTF. When the key fields contain a combination of columns whose combined number of bytes exceeds 1000, the installation will bail.
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).
In categorylinks, you need to change the following line:
KEY cl_sortkey(cl_to,cl_sortkey),
to
KEY cl_sortkey(cl_to(253),cl_sortkey),
In jobs, you need to change
KEY (job_cmd, job_namespace, job_title)
to
KEY (job_cmd(166), job_namespace, job_title(166))
This guarantees that they keys are short enough so that the install won't bail.
Where you need to change this, I'll put up in a second.
References
These bugs are actually filed on the MediaWiki bugzilla. See
