MariaDB 13: Oracle PL/SQL Boost & Dev Experience

Bridging the Oracle Gap

MariaDB 13's release marks a crucial step in its strategy to court enterprise users, particularly those migrating from Oracle. The native support for REF CURSOR and RECORD types in routine parameters and function return values is a standout feature, directly addressing a major pain point for Oracle PL/SQL developers. This significantly lowers the barrier to entry for Oracle-centric organizations considering MariaDB as an alternative, potentially accelerating their cloud migration or modernization efforts. The enhanced RETURNING clause, now supporting UPDATE and providing access to OLD_VALUE(), further streamlines common data manipulation tasks, reducing the need for multiple round trips and improving application performance. The improvements to the optimizer hint framework, with automatic query block naming for views, CTEs, and derived tables, demonstrate a commitment to making performance tuning more accessible and less error-prone, especially in complex query environments. For developers, this translates to more powerful and intuitive tools for managing data and optimizing query execution. The observability enhancements, such as exposing init_rpl_role as a system variable and including CREATE_OPTIONS in I_S.STATISTICS and I_S.COLUMNS, are vital for modern DevOps practices, enabling better automation, monitoring, and troubleshooting of database environments. These features collectively enhance the operational efficiency and maintainability of MariaDB deployments.

However, a key limitation to note is that REF CURSOR and RECORD types are not yet supported as parameters or return types for non-package (global) routines. While the focus on Oracle compatibility is commendable, this restriction might hinder complete migration for certain application architectures. Additionally, while the RETURNING clause is improved, its current limitation to single-table statements means complex multi-table updates will still require more elaborate logic. MariaDB's rolling release model, while fast-paced, means that organizations prioritizing extreme long-term stability might still lean towards LTS versions, though the mention of MariaDB 13.3 as the next LTS release indicates a clear roadmap. The impact of these features is substantial for developers and DBAs working with Oracle PL/SQL, legacy enterprise applications, or those seeking more robust developer tooling and operational insights. It positions MariaDB as a more compelling choice for heterogeneous environments and for organizations looking to leverage open-source databases without sacrificing critical enterprise-grade functionalities.

Key Points

• MariaDB Community Server 13.0 is now generally available.
• Expanded Oracle compatibility with native support for REF CURSOR and RECORD types in routine parameters and function return values.
• RETURNING clause enhanced for UPDATE statements, allowing retrieval of modified rows and OLD_VALUE() in a single round trip.
• Optimizer hint framework improved with automatic query block naming for Views, CTEs, and derived tables, simplifying targeting.
• Enhanced observability and administration with init_rpl_role exposed as a system variable and CREATE_OPTIONS available in I_S.STATISTICS and I_S.COLUMNS.
• System variables now indicate deprecation status in I_S.SYSTEM_VARIABLES.
• MariaDB follows a rolling release model, with 13.3 planned as the next LTS release.

---

📖 Source: MariaDB 13 Expands Oracle Compatibility and Improves Developer Experience and Observability