Last modified: 2010-05-15 15:52:02 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 10039 - MySQL 5 binary schema broken
MySQL 5 binary schema broken
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Database (Other open bugs)
1.10.x
All All
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-05-27 09:06 UTC by Tim Starling
Modified: 2010-05-15 15:52 UTC (History)
1 user (show)

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


Attachments

Description Tim Starling 2007-05-27 09:06:36 UTC
CHAR fields with a table default charset of "binary" are silently converted to the BINARY field type, which automatically pads data with null characters on the right. This occurs in a number of places in the MW 1.10 binary schema. These null characters are exposed to MediaWiki causing various bugs. The solution (discussed with Domas on #mediawiki) is to use VARCHAR instead of CHAR in all the relevant places, which will be silently converted to VARBINARY. VARBINARY has a length byte and is thus capable of binary-safe storage of variable-length fields.
Comment 1 Rob Church 2007-07-09 08:33:38 UTC
Fixed by Tim in r23239, r23246 and r23247; backported to 1.10 branch in r23651 and r23652.

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


Navigation
Links