Page MenuHomePhabricator

Use utf8_general_ci for "sort" columns in old MySQL
ClosedPublic

Authored by epriestley on Feb 26 2015, 4:00 PM.
Tags
None
Referenced Files
F15434870: D11893.id.diff
Tue, Mar 25, 5:47 AM
F15429691: D11893.id28652.diff
Mon, Mar 24, 3:38 AM
F15407011: D11893.diff
Tue, Mar 18, 3:11 PM
F15389335: D11893.id28655.diff
Sat, Mar 15, 5:08 AM
F15382523: D11893.diff
Fri, Mar 14, 12:49 PM
Unknown Object (File)
Feb 9 2025, 6:06 PM
Unknown Object (File)
Feb 8 2025, 2:45 AM
Unknown Object (File)
Feb 8 2025, 2:45 AM
Subscribers

Details

Summary

Fixes T7287. This trades off 4-byte character support for case insensitivity in these columns, which is a much better trade on the balance.

Also adds more warnings about old MySQL. Note that we already issue a warning when you run "storage adjust" (which I've made stronger) and already "strongly recommend" MySQL 5.5 or newer in the install documentation.

Test Plan
  • Ran storage adjust --disable-utf8mb4 to go to old definitions, then ran storage adjust to get back to the new ones. Everything seemed OK in both cases.
  • Verified that utf8mb4 data can be migrated out of these colums with --unsafe (which will truncate).
  • Verified that manual explains this.
  • Faked my way into the setup warning.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Use utf8_general_ci for "sort" columns in old MySQL.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Feb 26 2015, 6:08 PM
This revision was automatically updated to reflect the committed changes.