Last checked and updated on 12 Jun 2026
What Is New in MariaDB 12.0
MariaDB 12.0 is a community release that introduces a range of new features, performance enhancements, and bug fixes. It's built on the foundation of previous versions with a focus on stability and incremental improvements for developers and database administrators.
| Category | Key Changes |
|---|---|
| New Features | System-versioned table syntax, New optimizer hints, JSON_TABLE() support |
| Improvements | InnoDB performance, Optimizer enhancements, Better type handling |
| Bug Fixes | Numerous fixes for replication, partitioning, and specific SQL operations |
What new syntax was added for system-versioned tables?
MariaDB 12.0 expands support for system-versioned tables with new syntax options. You can now use a WITHOUT SYSTEM VERSIONING clause to alter a table and remove its versioning feature.
This provides more flexibility for managing temporal tables. In practice, it means you can easily convert a system-versioned table back to a standard table without needing to recreate it from scratch.
How did the optimizer get better in 12.0?
The query optimizer received several key enhancements. New optimizer hints were introduced, giving developers more control over query execution plans.
Improvements were made to the handling of prepared statements and the GROUP BY operation. These changes help in generating more efficient execution plans, which can lead to faster query performance for complex workloads.
What JSON functionality was added?
MariaDB 12.0 added support for the JSON_TABLE() function. This function allows you to transform JSON data into a relational table format that can be queried with standard SQL.
This is particularly useful when you need to join JSON data with other tables in your database. It bridges the gap between document-oriented and relational data models within the same query.
Were there any InnoDB storage engine improvements?
Yes, several InnoDB enhancements were included in this release. These improvements focus on overall performance and reliability of the storage engine.
The changes help with better resource management and transaction handling. For heavy write workloads, these optimizations can result in better throughput and more consistent performance.
What type handling changes should developers know about?
MariaDB 12.0 introduced better handling of the DOUBLE data type. The update ensures more consistent behavior when working with double-precision floating-point numbers.
This matters because it reduces unexpected results in mathematical calculations. Applications dealing with scientific or financial data will benefit from this increased precision and reliability.
FAQ
Can I use the new system-versioned table syntax to convert existing tables?
Yes, the new WITHOUT SYSTEM VERSIONING syntax allows you to alter existing system-versioned tables to remove the versioning feature without dropping and recreating the table.
Does JSON_TABLE() work with nested JSON structures?
Yes, the JSON_TABLE() function can handle complex JSON documents, including nested objects and arrays, transforming them into a relational format that can be queried with SQL.
Are the new optimizer hints backward compatible?
The new optimizer hints are additive and don't break existing queries. However, using them might change execution plans, so testing is recommended when applying them to production queries.
What's the impact of the DOUBLE type handling changes?
The improvements provide more consistent behavior for double-precision floating-point operations, reducing rounding errors and unexpected results in mathematical calculations.
Should I expect performance improvements with InnoDB in 12.0?
Yes, the InnoDB enhancements in MariaDB 12.0 focus on better resource management and transaction handling, which can lead to improved performance for write-intensive workloads.