Last modified: 2010-05-15 15:52:02 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.
Fixed by Tim in r23239, r23246 and r23247; backported to 1.10 branch in r23651 and r23652.