Issue Bug Closed

#101719Environment Status reports: MySQL database character set check failed

Timo Gurr 08/21/23, 09:26 updated 07/09/24, 15:19

Description

After upgrading MariaDB of an existing installation currently at TYPO3 LTS 11.5.30 from MariaDB 10.5.21 to MariaDB 10.11.4 the TYPO3 Environment Status now reports:

MySQL database character set check failed
Checking database character set failed, got key "utf8mb3" instead of "utf8 or utf8mb4"

https://get.typo3.org/version/11#system-requirements lists MariaDB >= 10.2.7 <= 10.11.99

According to

https://mariadb.com/kb/en/unicode/
https://stackoverflow.com/questions/63414060/is-utf8-in-mariadb-still-utf8mb3

utf8 is an alias for utf8mb3 on MariaDB >= 10.6 and until MariaDB 10.5 utf8mb3 was an alias for utf8. From MariaDB 10.6, utf8 is by default an alias for utf8mb3 – if I got things right.

So for example phpMyAdmin shows the following collation for the TYPO3 database:

before upgrade: MariaDB 10.5.21 – utf8_general_ci
after upgrade: MariaDB 10.11.4 – utf8mb3_general_ci

TYPO3 11.5.30 currently probably only checks for the strings “utf8” and “utf8mb4” and thus complains about “utf8mb3” not knowing it’s actually still plain “utf8” on MariaDB 10.11.4(?).

Reviews 3

Files 1

History 37

  1. Timo Gurr changed subject MySQL database character set check failed Environment Status reports: MySQL database character set check failed 08/21/23, 09:28

  2. Gerrit Code Review pushed patch set 1 for main to change 80632 status New Under Review 08/22/23, 11:43

  3. Gerrit Code Review pushed patch set 2 for main to change 80632 08/22/23, 11:52

  4. Gerrit Code Review pushed patch set 1 for 12.4 to change 80615 08/22/23, 12:10

  5. Gerrit Code Review pushed patch set 1 for 11.5 to change 80616 08/22/23, 12:16

  6. Timo Gurr commented and changed status Under Review Resolved done 0 % 100 % 08/22/23, 12:30

    Applied in changeset commit:5a93c81bf4ad0a675c1a970026b8e5b5c0227947.

  7. Benni Mack changed status Resolved Closed 07/09/24, 15:19