Last modified: 2012-08-27 01:32:54 UTC
I'll re-test (and update this ticket) tomorrow to be sure this isn't a problem with my update schema-separation code, but updating from 1.11 to 1.19 didn't apply this patch so that I have the indices it creates. "show create table" looks like this: CREATE TABLE `logging` ( `log_type` varbinary(32) NOT NULL, `log_action` varbinary(32) NOT NULL, `log_timestamp` binary(14) NOT NULL DEFAULT '19700101000000', `log_user` int(10) unsigned NOT NULL DEFAULT '0', `log_namespace` int(11) NOT NULL DEFAULT '0', `log_title` varchar(255) CHARACTER SET latin1 COLLATE latin1_bin NOT NULL DEFAULT '', `log_comment` varchar(255) NOT NULL DEFAULT '', `log_params` blob NOT NULL, `log_id` int(10) unsigned NOT NULL AUTO_INCREMENT, `log_deleted` tinyint(3) unsigned NOT NULL DEFAULT '0', `log_user_text` varchar(255) CHARACTER SET latin1 COLLATE latin1_bin NOT NULL DEFAULT '', `log_page` int(10) unsigned DEFAULT NULL, PRIMARY KEY (`log_id`), KEY `type_time` (`log_type`,`log_timestamp`), KEY `user_time` (`log_user`,`log_timestamp`), KEY `page_time` (`log_namespace`,`log_title`,`log_timestamp`), KEY `times` (`log_timestamp`), KEY `type_action` (`log_type`,`log_action`,`log_timestamp`) ) ENGINE=InnoDB AUTO_INCREMENT=12803 DEFAULT CHARSET=latin1
Closing WORKSFORME. There is something else going on in my particular case. When I installed 1.11 and then upgraded, everything, including my schema-separation code, worked.
