wiki.techinc.nl/maintenance/archives/patch-pt_title-encoding.sql

-- pt_title was accidentally left with the wrong collation.
-- This might cause failures with JOINs, and could protect the wrong pages
-- with different case variants or unrelated UTF-8 chars.
ALTER TABLE /*$wgDBprefix*/protected_titles
  CHANGE COLUMN pt_title pt_title varchar(255) binary NOT NULL;
* (bug 13768) pt_title field encoding fixed pt_title field in page_protections was added without a binary marker when used on non-binary schema. This means you get false matches for ASCII case-insensitive bits, and probably for horribly wrong UTF-8 mish-mashes as well. Adds an updated to fix the field's encoding to binary, matching all our other title keys, so you can join and get correct matches. Revert r33473, which seems to assume that pt_title is supposed to be case-insensitive. (Even if it was, it woudln't work correctly as written.) 2008-04-17 19:11:36 +00:00			`-- pt_title was accidentally left with the wrong collation.`
			`-- This might cause failures with JOINs, and could protect the wrong pages`
			`-- with different case variants or unrelated UTF-8 chars.`
			`ALTER TABLE /$wgDBprefix/protected_titles`
Self-revert r80547 per CR, breaks stuff and is undesirable 2011-01-20 23:56:47 +00:00			`CHANGE COLUMN pt_title pt_title varchar(255) binary NOT NULL;`