Manual talk:Upgrading to 1.11

Alternative 1: phpShell
This is only working when you have php.exe in a path. If you don't have that you have to use a command-line like: $ "c:/phpdirectory/php.exe" "c:/wikidirectory/maintenance/update.php"

If you are using windows you can start cmd.exe and put above line without the $ and it works as well. Londenp 15:18, 14 September 2007 (UTC)

Problem with change to categorylinks index
I am using PHP5 and MYSQL5. Got error: Checking if categorylinks index cl_sortkey includes field cl_from... ...index cl_sortkey on table categorylinks has no field cl_from; adding Query "ALTER TABLE `wm_categorylinks` DROP INDEX cl_sortkey, ADD INDEX cl_sortkey(cl_to, cl_sortkey, cl_from) " failed with error code "Specified key was too long; max key length is 1000 bytes

(hostname here)

This was similar to a problem I had with the wm_job(?) table on first installation, which I think related to an assumption that databases used latin1 characters rather than utf8 (which use 3 bytes per character instead of one). So I made the following change to /maintenance/archives/patch-categorylinksindex.sql -- JW adding (160) to fix problem ALTER TABLE /*$wgDBprefix*/categorylinks DROP INDEX cl_sortkey, ADD INDEX cl_sortkey(cl_to(160), cl_sortkey, cl_from);

By the way the table, before the change above looked like this: mysql> show columns from wm_categorylinks; +--+-+--+-+---+---+ +--+-+--+-+---+---+ +--+-+--+-+---+---+ 4 rows in set (0.00 sec)
 * Field       | Type            | Null | Key | Default           | Extra |
 * cl_from     | int(8) unsigned | NO   | MUL | 0                 |       |
 * cl_to       | varchar(255)    | NO   | MUL |                   |       |
 * cl_sortkey  | varchar(86)     | NO   |     |                   |       |
 * cl_timestamp | timestamp      | NO   |     | CURRENT_TIMESTAMP |       |

This worked but I would appreciate a comment on whether the reduced key size will create problems for the future. Thanks. Jonathan3 00:51, 15 September 2007 (UTC)