Default character set divergence between Windows and Linux table creation in MariaDB

MariaDB's default character set for newly created tables varies by operating system: latin1 on Windows and utf8mb3 on Linux, as documented since early releases. This platform-dependent fallback can produce inconsistent schema outputs when the same initialization scripts are deployed across mixed environments. A team migrating a workload from a Linux-based container to a Windows server may observe that newly provisioned tables adopt latin1 as the default, potentially causing silent data truncation for multilingual content unless explicitly overridden per table. The server configuration parameters character_set_server and collation_server can be set at startup, but their interaction with the OS-driven default during table creation remains ambiguous in the documentation, particularly for dynamic provisioning without a restart. Given an application schema relying on utf8mb4, it is unclear whether setting character_set_server=utf8mb4 at startup propagates to new tables without explicit CHARSET clauses, or whether the OS fallback takes precedence. It is also uncertain if the behavior differs between InnoDB and Aria storage engines during a single session.

• Does the server-level character_set_server directive fully determine the default character set for new tables across all platforms, or does the OS-specific fallback persist?
• Is there a documented, runtime method to enforce a uniform default character set for all subsequently created tables without per-table ALTER statements?
• How does the default character set behavior differ between InnoDB and Aria storage engines when tables are created during a single server session?