The release of the MariaDB database management system 13.0.2 has been presented, marked as the first stable release of the 13.0 branch. The MariaDB 13.0 branch is classified as rolling releases, continuing the gradual development of functionality and supported until the stable release of the next branch. At the same time, the MariaDB 13.1.1 release, which has release candidate status, is available.
The MariaDB project develops a fork from MySQL, preserving backward compatibility and distinguished by the integration of additional storage engines and enhanced capabilities. The development of MariaDB is overseen by the independent MariaDB Foundation in accordance with an open and transparent development process that is not dependent on individual vendors. MariaDB is supplied instead of MySQL in many Linux distributions (RHEL, SUSE, Fedora, openSUSE, Slackware, OpenMandriva, ROSA, Arch Linux, Debian) and is implemented in major projects such as Wikipedia, Google Cloud SQL, and Nimbuzz.
Among the changes in the MariaDB 13.0 branch:
- The expression "TYPE .. IS REF CURSOR" has been added for declaring a reference data type for a cursor that can be used to return the result of an SQL query or a set of rows from stored procedures and functions.
- The use of the RECORD type has been enabled in procedure parameters and in the values returned by functions.
- An optimizer hint QB_NAME() has been added, allowing a name to be assigned to a query block for the subsequent application of optimization instructions for that block.
- Support has been added for executable comments "/*!! ... */" that are revealed only in versions older than the specified one. For example, if in MariaDB version 10.0 it is necessary to execute the statement "CREATE OR REPLACE TABLE", and in older versions — "CREATE TABLE IF NOT EXISTS": CREATE /*!100000 OR REPLACE */ TABLE /*!!100000 IF NOT EXISTS */ t1 …
- A column IS_DEPRECATED has been added to the INFORMATION_SCHEMA.SYSTEM_VARIABLES table to mark deprecated variables, and in the INFORMATION_SCHEMA.STATISTICS and INFORMATION_SCHEMA.COLUMNS tables, a column CREATE_OPTIONS has appeared with details about engine-specific capabilities of the "CREATE TABLE" expression.
- The ability to configure the time format specified in the plugin logs for auditing has been provided.
- Atomic execution of the "CREATE OR REPLACE TABLE" operation has been ensured.
- The "UPDATE ... RETURNING" construct has been implemented, allowing rows to be updated and their modified values to be returned immediately.
- A new variable innodb_log_archive has been added to enable the mode for saving files with WAL logs (instead of cyclically overwriting the log in a single file, once filled, the record switches to a new file).
- The MEMORY storage engine has accelerated the operation of indexes (UNIQUE INDEX) for CHAR type columns.
Source: opennet.ru
