MariaDB 13.0.2 has been released, marking it as the first stable release of the 13.0 branch. MariaDB 13.0 is considered a rolling release, continuing the gradual development of functionality and being maintained until the stable release of the next branch. MariaDB 13.1.1, a release candidate, is also available.
The MariaDB project develops a fork of MySQL that maintains backward compatibility and features the integration of additional storage engines and advanced features. MariaDB's development is overseen by the independent MariaDB Foundation, following an open and transparent development process independent of individual vendors. MariaDB is shipped as a replacement for MySQL in many distributions. Linux (RHEL, SUSE, Fedora, openSUSE, Slackware, OpenMandriva, ROSA, Arch Linux, Debian) and has been implemented in such large projects as Wikipedia, Google Cloud SQL and Nimbuzz.
Changes in the MariaDB 13.0 branch include:
- Added the "TYPE .. IS REF CURSOR" statement to declare a reference data type for a cursor that can be used to return the result of an SQL query or a rowset from stored procedures and functions.
- The ability to use the RECORD type in procedure parameters and in function return values has been introduced.
- Added the QB_NAME() optimizer hint, which allows you to assign a name to a query block for subsequent application of optimization instructions for this block.
- Added support for executable comments "/*!! … */" that expand only in versions older than the specified one. For example, if you need to execute the "CREATE OR REPLACE TABLE" statement in MariaDB 10.0, and "CREATE TABLE IF NOT EXISTS" in earlier versions: CREATE /*!100000 OR REPLACE */ TABLE /*!!100000 IF NOT EXISTS */ t1 …
- The INFORMATION_SCHEMA.SYSTEM_VARIABLES table now has an IS_DEPRECATED column to mark deprecated variables, and the INFORMATION_SCHEMA.STATISTICS and INFORMATION_SCHEMA.COLUMNS tables now have a CREATE_OPTIONS column to provide information about engine-specific capabilities of the CREATE TABLE statement.
- The ability to customize the time format indicated in the plugin logs for audit purposes has been provided.
- Atomic execution of the "CREATE OR REPLACE TABLE" operation is ensured.
- The "UPDATE … RETURNING" construct has been implemented, allowing you to update rows and immediately return their changed values.
- Added the innodb_log_archive variable to enable the mode of saving files with WAL logs (instead of cyclically rewriting the log in one file, after it is full, the recording switches to a new file).
- In the MEMORY engine, the operation of indexes (UNIQUE INDEX) for CHAR columns has been accelerated.
Source: opennet.ru
