MariaDB Utf8mb4_0900_ai_ci Supported
You can make mariadb utf8mb4_0900_ai_ci supported in modern releases or map it to native sorting rules. You change the schema text or update the engine so imports do not fail. Teams often run into this sorting rule when moving dump files from MySQL into MariaDB. To fix import errors fast, engineers often log in with broad admin permissions on production servers. Using wide database roles for schema fixes puts live user data at high risk. How mariadb utf8mb4_0900_ai_ci supported rules work A d
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
You can make mariadb utf8mb4_0900_ai_ci supported in modern releases or map it to native sorting rules. You change the schema text or update the engine so imports do not fail. Teams often run into this sorting rule when moving dump files from MySQL into MariaDB. To fix import errors fast, engineers often log in with broad admin permissions on production servers. Using wide database roles for schema fixes puts live user data at high risk.
How mariadb utf8mb4_0900_ai_ci supported rules work
A database collation is a set of rules that tells the engine how to sort text. The 0900 part in the name refers to the ninth version of the Unicode sorting standard. The ai part means accent insensitive, while the ci part means case insensitive. MySQL made this specific collation its default setting for four-byte UTF-8 text in recent major versions. For a long time, MariaDB did not include this exact MySQL collation name in its catalog.
When a team tried to load a MySQL dump file, MariaDB stopped the import right away. Recent MariaDB versions added built-in support and mapping for these Unicode nine sorting rules. If you run an older MariaDB engine, you must replace the collation string before importing data. You can swap it for a native general or Unicode sorting rule that matches your text needs. Both methods require schema permissions to alter tables, columns, and character sets across your target database.
What native collation updates solve and leave open
Updating the collation settings solves the immediate compatibility crash during a database migration or restore job. Once the sorting rules match what the engine expects, your tables load and index text well. Your app can then run text searches and sort rows without throwing character set errors.
Still, the native database role setup leaves a big gap during these maintenance tasks. Native database roles only check who logs in and which tables that account can alter. To fix collation errors across many tables, engineers usually receive full alter and read rights. Once logged in, nothing stops that user from reading sensitive columns or dropping the wrong table. Database roles cannot inspect individual queries in flight or mask private fields during a live debug session. If a script runs a broad select statement, raw emails and card numbers return in plain text.
GitLab CI Security + AI Agent Security: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Safe habits for schema and collation changes
Before changing any character set or sorting rule, test the dump file on a staging copy. Changing a collation on a live table causes the engine to rebuild the text indexes. On large tables, this index rebuild locks writes and slows down your main app. Always check if unique text indexes will break when accent rules change during the swap. Two words that looked different under an old rule might look identical under an accent-insensitive rule.
You should also limit what maintenance accounts can do when engineers fix import bugs. Separate the duties of altering empty table structures from reading live production rows. When staff must query live tables to check text sorting, rewrite sensitive fields like phone numbers in results. Recording every query statement alongside the user identity also helps audit teams track every schema change.
Check MySQL queries and results on the wire
MySQL grants control who logs in. They do not check single queries or mask sensitive columns once a session starts. With hoop.dev, you run an open-source proxy, a sidecar for your MySQL. It runs next to MySQL, RDS, or Aurora and reads the MySQL wire protocol.
Multi-statement batches and prepared queries are split and checked one by one by hoop.dev guardrails. When a rule refuses a query, MySQL returns a native error packet with your message. On the response path, hoop.dev data masking rewrites string values in returned rows that match your rules. Every query and decision is logged per resource. See the MIT-licensed project on GitHub.
Frequently asked questions
Why does my MySQL dump fail with an unknown collation error in MariaDB?
MySQL uses its own default Unicode sorting name that older MariaDB releases do not recognize. You must upgrade MariaDB to a version with compatibility support or change the collation name in the file.
Does changing a table collation affect existing data or indexes?
Yes, changing a table collation forces the database to rebuild text indexes using the new sorting rules. If the new rule is accent insensitive, duplicate key errors can happen on unique text columns.
How can teams run collation fixes without exposing sensitive table data?
Teams should avoid sharing static root accounts for migration fixes. Instead, check every query in flight, block unsafe drops, and mask national IDs or emails in query results.
Related guides
In this post