Page MenuHomePhabricator

When "utf8mb4" is available, use it as the default client charset when invoking standalone "mysql" commands
ClosedPublic

Authored by epriestley on Aug 27 2019, 10:33 PM.
Tags
None
Referenced Files
F15334506: D20742.id49455.diff
Sat, Mar 8, 10:04 AM
F15333399: D20742.id49456.diff
Sat, Mar 8, 2:08 AM
F15333136: D20742.id.diff
Sat, Mar 8, 12:14 AM
Unknown Object (File)
Tue, Feb 25, 11:19 PM
Unknown Object (File)
Tue, Feb 25, 11:04 PM
Unknown Object (File)
Tue, Feb 25, 10:18 PM
Unknown Object (File)
Tue, Feb 25, 10:15 PM
Unknown Object (File)
Tue, Feb 25, 1:44 PM
Subscribers
None

Details

Summary

Fixes T13390. We have some old code which doesn't dynamically select between "utf8mb4" and "utf8". This can lead to dumping utf8mb4 data over a utf8 connection in bin/storage dump, which possibly corrupts some emoji/whales.

Instead, prefer "utf8mb4" if it's available.

Test Plan

Ran bin/storage dump and bin/storage shell, saw sub-commands select utf8mb4 as the client charset.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable