Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 109960 - dev-db/mysql-4.1.14 with USE="...utf8" has problem with mediawiki-1.3.16
Summary: dev-db/mysql-4.1.14 with USE="...utf8" has problem with mediawiki-1.3.16
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High minor (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
: 137548 180280 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-10-20 14:13 UTC by Henri
Modified: 2007-05-29 21:10 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henri 2005-10-20 14:13:37 UTC
dev-db/mysql-4.1.14 with USE="... utf8" has problem with mediawiki-1.3.16 

Problem can be solved by using USE="-utf8".

The bug is described by mysql.
http://bugs.mysql.com/bug.php?id=4541.

I'll hope this will help someone, but fixing to the bug is in upstream.

Reproducible: Always
Steps to Reproduce:
Comment 1 Henri 2005-10-20 14:15:19 UTC
I'll hope this will help someone, but fixing to the bug is in upstream.
Comment 2 Henri 2005-10-20 14:25:45 UTC
See also:
http://bugzilla.wikipedia.org/show_bug.cgi?id=1322

Given error message was:
Specified key was too long; max key length is 1000 bytes


Comment 3 Francesco R. (RETIRED) gentoo-dev 2005-10-22 10:52:35 UTC
this is referred upstream as feature request 4541

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

lurking the commit mailing list look like something has been done for amd64
expanding the keys to 3000 bytes = 1000 chars in utf8 encoding.
however 5.0.13_rc amd64 still give an error:
#1071 - Specified key was too long; max key length is 1000 bytes

Comment 4 Jakub Moc (RETIRED) gentoo-dev 2006-06-22 08:08:59 UTC
*** Bug 137548 has been marked as a duplicate of this bug. ***
Comment 5 Jakub Moc (RETIRED) gentoo-dev 2007-05-29 21:10:57 UTC
*** Bug 180280 has been marked as a duplicate of this bug. ***