The idm and idm_staging database on M5 appears to have been created as "binary" and not "utf8mb4".
The databases will be used for a Django project, which is rather picky about database encoding, and supports only utf8.
Currently there's no data in either database, and they can be deleted, if that makes the task of changing the encoding easier.
I don't believe I specified encoding on the original task, which I should have, sorry.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | SLyngshede-WMF | T338008 IDM Production Checklist for initial signup milestone | |||
| Resolved | Marostegui | T339327 Change IDM database characther encoding |
root@db1176.eqiad.wmnet[(none)]> alter database idm DEFAULT CHARACTER SET utf8mb4; Query OK, 1 row affected (0.001 sec) root@db1176.eqiad.wmnet[(none)]> show create database idm; +----------+--------------------------------------------------------------------------------------------+ | Database | Create Database | +----------+--------------------------------------------------------------------------------------------+ | idm | CREATE DATABASE `idm` /*!40100 DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci */ | +----------+--------------------------------------------------------------------------------------------+ 1 row in set (0.001 sec)