This bug looks to be caused by the default charset for the databases being:
CHARACTER SET latin1 COLLATE latin1_swedish_ci
These are shown in the schema, even though under General Settings, utf8mb_unicode_ci is the "Server connection collation".
This is likely an artifact from when the AGAGD was first acquired from the EGF.
We should be able to update this value to:
CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci (looks like we are on version 5.7 of MySQL)
Please review the following documentation before making changes, as the CHARACTER SET we choose can affect things like varchar value comparisons and sorting (eg. a and á may or may not be treated as equivalent)
e.g. https://agagd.usgo.org/player/24898/