I'm seeing the same thing.
What are the long term consequences of changing the key length in order to use this
version?
Also, since bug 1322 was first reported in 1.4beta4 and 1.5alpha1, and I didn't have a
problem with versions 1.5.3-8, why would this bug now effect my system when going to
1.6.7?
Thanks
-Ira
>> felipe.sanches(a)gmail.com 7/6/2006 6:00:15 pm
>>>
Some time ago Rob Church told in this list that :
This is a known issue for some users, and various
suggestions, advice
and workarounds are available at
http://bugzilla.wikimedia.org/show_bug.cgi?id=1322. I'd check to see
if one of these works.
although bug 1322 is curently invalid in bugzilla.
>> felipe.sanches(a)gmail.com 7/6/2006 5:55:40 pm
>>>
MediaWiki 1.6.7 Updater
Going to run database updates for cee
Depending on the size of your database this may take a while!
Abort with control-c in the next five seconds...0
...hitcounter table already exists.
...querycache table already exists.
...objectcache table already exists.
...categorylinks table already exists.
...logging table already exists.
...validate table already exists.
...user_newtalk table already exists.
...transcache table already exists.
...trackbacks table already exists.
...externallinks table already exists.
Creating job table...Query "CREATE TABLE `wikicee_job` (
job_id int(9) unsigned NOT NULL auto_increment,
job_cmd varchar(255) NOT NULL default '',
job_namespace int NOT NULL,
job_title varchar(255) binary NOT NULL,
job_params blob NOT NULL default '',
PRIMARY KEY job_id (job_id),
KEY (job_cmd, job_namespace, job_title)
) TYPE=InnoDB
" failed with error code "Specified key was too long. Max key length
is 500 (loc alhost)".
cee@bighead:~/www/wiki/maintenance>
Can anybody help me?