Bug 137548

Summary:	mediawiki >=1.6.3 needs more testing for install
Product:	Gentoo Linux	Reporter:	Philippe Trottier (RETIRED) <tchiwam>
Component:	Current packages	Assignee:	Christian Parpart (RETIRED) <trapni>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	High
Version:	2006.0
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Philippe Trottier (RETIRED) gentoo-dev

2006-06-22 00:56:27 UTC

If there is a problem installing, something related to 

>     * Creating tables... using MySQL 4 table defs...Query "CREATE TABLE
> `gw_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 1024 bytes (localhost)".

This is a good link on a work around:

http://mail.wikipedia.org/pipermail/mediawiki-l/2006-April/011707.html

Can you test this with other platforms ?

Ill probably close this bug if you can't reproduce the problem, you have to install a brand new mediawiki for it to show up.


dev-lang/php-5.1.4  USE="apache2 berkdb bzip2 cgi cli crypt exif gd gdbm gmp imap ldap ming mysql ncurses nls pcre readline reflection sasl session snmp sockets spell spl ssl truetype unicode xml zlib -apache -bcmath -calendar -cdb -cjk -ctype -curl -curlwrappers -dbase -debug -discard-path -doc -fastbuild -firebird -flatfile -force-cgi-redirect -ftp -gd-external -hardenedphp -hash -iconv -inifile -interbase -iodbc -ipv6 -kerberos -mcve -memlimit -mhash -msql -mssql -mysqli -odbc -pcntl -pdo -pdo-external -posix -postgres -qdbm -recode -sapdb -sharedext -sharedmem -simplexml -soap -sqlite -sysvipc -threads -tidy -tokenizer -vm-goto -vm-switch -wddx -xmlreader -xmlrpc -xmlwriter -xpm -xsl -yaz -zip"

Comment 1 Jakub Moc (RETIRED) gentoo-dev

2006-06-22 08:08:59 UTC

http://bugs.mysql.com/bug.php?id=4541

You can setup the db with latin-1 character set instead of utf-8 as a
workaround. No idea when MySQL will finally do something about this. :/


*** This bug has been marked as a duplicate of 109960 ***