An existing .NET Framework application moves from MySQL to MariaDB, and a connection or query now fails with a message like Character set 'utf8mb3' is not supported . Where should the investigation start?
My answer: with the connector that the running application actually loads, then the server's character set settings, and only after that the schema. Changing columns before you understand the failure can turn a dependency problem into a data migration.
This is a diagnostic guide built from official documentation, which I re-read on November 2, 2026. I did not reproduce the exception for this article, and the snippets below are diagnostics to adapt, not tested fixes.
Why the name utf8mb3 appears at all
Two documented facts fit together here.
The MariaDB OLD_MODE documentation says that from MariaDB 10.6.1, "the main name of the previous 3-byte utf8 character set was changed to utf8mb3 ". With the UTF8_IS_UTF8MB3 flag set, utf8 is an alias for utf8mb3 .…