MariaDB 11.8.1 Release Notes

Download Release Notes Changelog Overview of 11.8

Release date: 13 Feb 2025

MariaDB 11.8 is a current long-term development series of MariaDB. It is an evolution of MariaDB 11.7 with several entirely new features.

MariaDB 11.8.1 is a Release Candidate (RC) release.

For an overview of MariaDB 11.8 see the What is MariaDB 11.8? page.

Thanks, and enjoy MariaDB!

Notable Items

Storage Engines

• Fix assertion failure on cascading foreign key update of table with vcol index in parent ()

Optimizer

• Fix possibly wrong result using a degenerated subquery (SELECT ) with window function ()

• Conditions with SP local variables are now pushed into derived table. Previous behaviour caused slow performance and table scans instead of using the pushed down condition ()

• Support ORDER BY and LIMIT for multi-table DELETE, index hints for single-table DELETE. ()

• Optimizer can now use indexed virtual columns in WHERE/ON clauses for improved query performance. (

PL/SQL

• It is now possible to define default values (or expressions) for parameters to stored procedures, stored functions and UDFs ()

• New DECLARE TYPE type_name IS RECORD (..) with scalar members in stored routines ()

• It was not possible to use a package body variable as a fetch target, instead error "Undeclared variable" was returned. ()

• Fix trigger created with "" which is adding rows to another table using "FOR EACH ROW insert into table2(id, name) values (NEW.id, NEW.name);" that did not work correctly when if bulk inserts are used by the application. Only the first row of the bulk insert would be added to the table ()

• A Trigger definition can now include column names for specifying the columns for which a trigger should be called ()

• Fix possible hang or crash where zero offset applied to null pointer ()

• Comparison of UUID v1 and V6 could return incorrect results ()

• Fix possible runtime error caused by XA RECOVER applying a zero offset to a null pointer ()

• Fix issue where functions in default values in tables with certain character sets could break SHOW CREATE and mariadb-dump ()

• OS character sets "utf8" and "utf-8" now map to MariaDB character set "utf8mb4" for full UTF-8 support. ()

• Calling a stored routine that executes a join on three or more tables and referencing not-existent column name in the USING clause could previously result in a crash on its second invocation. ()

Scripts & Clients

• When using with --innodb-optimize-keys, secondary index creation is delayed until after data load, potentially improving load speed. ()

Changelog

For a complete list of changes made in , with links to detailed information on each push, see the .

Contributors

For a full list of contributors to , see the .