Last modified: 2011-05-15 10:13:52 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 21407 - codereview.sql not utf-8 clean
codereview.sql not utf-8 clean
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
CodeReview (Other open bugs)
unspecified
PC Linux
: Low critical with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://svn.wikimedia.org/viewvc/media...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-11-04 10:42 UTC by sean dwyer
Modified: 2011-05-15 10:13 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description sean dwyer 2009-11-04 10:42:28 UTC
Running MySQL 5.051a-24 configured for utf8 on a Debian Linux box. Mediawiki 1.16alpha r58426.

Get the following error on loading codereview.sql:

ERROR 1071 (42000) at line 79: Specified key was too long; max key length is 1000 bytes

The culprit is: 

unique key (ca_user_text, ca_repo_id, ca_author); in table code_authors

which appears to be too long for my utf8 installation.

Tested the table without the key and the extension will run with broken functionality.
Comment 1 sean dwyer 2009-11-06 22:00:52 UTC
By removing it in initial import and then adding it alternatively in phpmyadmin with collate latin1_bin and utf8_bin i can confirm that utf8 encoding breaks the unique key.
Comment 2 Chad H. 2009-11-28 04:08:47 UTC
Cf bug 9350 and bug 4445

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links