MariaDB 10.4 is the current development series of MariaDB. It is an evolution
of MariaDB 10.3 with several entirely new features not found anywhere else
and with backported and reimplemented features from MySQL.
This will be the first alpha release in the series.
Notable changes of this release include:
InnoDB
Added instant and changing of the order of columns ()
Reduced redo log volume for undo tablespace initialization ()
Removed crash-upgrade support for pre-10.2.19 TRUNCATE TABLE ()
Optimizer
()
Variables
Added the system variable ()
Removed the global status variable ().
General
IF NOT EXISTS clause added to and IF EXISTS clause added to and ()
The obsolete is no longer created ()
Support of brackets (parentheses) for specifying precedence in /
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 .
Do not use alpha releases in production!
Be notified of new MariaDB Server releases automatically by to the MariaDB Foundation community announce 'at' lists.mariadb.org announcement list (this is a low traffic, announce-only list). MariaDB plc customers will be notified for all new releases, security issues and critical bug fixes for all MariaDB plc products thanks to the Notification Services.
MariaDB may already be included in your favorite OS distribution. More information can be found on the page.
Improvements with SQL standard INTERVAL support to help functions
and return more predictable results.
Historically, MariaDB uses the TIME data type for both "time of the day"
values and "duration" values. In the first meaning the natural value range
is from '00:00:00' to '23:59:59.999999', in the second meaning the range is
from '-838:59:59.999999' to '+838:59:59.999999'.
To remove this ambiguity and for the SQL standard conformance we plan to
introduce a dedicated data type INTERVAL that will be able to store values
in the range at least from '-87649415:59:59.999999' to
'+87649415:59:59.999999', which will be enough to represent the time
difference between TIMESTAMP'0001-01-01 00:00:00' and TIMESTAMP'9999-12-31
23:59:59.999999'.
As a first step we support this range of values for intermediate
calculations when TIME-alike string and numeric values are used in INTERVAL
(i.e. duration) context, e.g. as the second argument of SQL functions
TIMESTAMP(ts,interval) and ADDTIME(ts,interval), so the following can now be
calculated: