USE whp;

-- v126's collation-fix migration converted the new account tables to
-- utf8mb4_general_ci, which was the WRONG direction: whp.sites.username and
-- whp.site_domains.fqdn are utf8mb4_unicode_ci. A LEFT JOIN against those
-- still throws "Illegal mix of collations" until the new tables match.
--
-- v126's migration won't re-run on hosts that already applied v126, so this
-- separate migration in a new version dir reconverts both tables to unicode_ci.
-- Idempotent — CONVERT TO with the target collation already in place is a no-op.
ALTER TABLE whp.accounts_disabled
    CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

ALTER TABLE whp.account_disable_audit
    CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
