MariaDB 10.10 stable release

The first stable release of the new MariaDB 10.10 (10.10.2) DBMS branch has been published, within which a branch from MySQL is being developed that maintains backward compatibility and is distinguished by the integration of additional storage engines and advanced features. MariaDB development is overseen by the independent MariaDB Foundation, following an open and transparent development process independent of individual vendors. MariaDB is shipped in place of MySQL on many Linux distributions (RHEL, SUSE, Fedora, openSUSE, Slackware, OpenMandriva, ROSA, Arch Linux, Debian) and has been adopted by major projects such as Wikipedia, Google Cloud SQL, and Nimbuzz.

Key improvements in MariaDB 10.10:

  • Added the RANDOM_BYTES function to get a random sequence of bytes of a given size.
  • Added INET4 data type to store IPv4 addresses in 4-byte representation.
  • The default parameters of the "CHANGE MASTER TO" expression have been changed, which now uses the GTID (Global Transaction ID) based replication mode if the master server supports this kind of identifier. The "MASTER_USE_GTID=Current_Pos" setting has been deprecated and the "MASTER_DEMOTE_TO_SLAVE" option should be used instead.
  • Extended optimizations for merge operations with a large number of tables, including the ability to use "eq_ref" to merge tables in any order.
  • UCA (Unicode Collation Algorithm) algorithms are implemented, defined in the Unicode 14 specification and used to determine sorting and collation rules taking into account the meaning of characters (for example, when sorting digital values, the presence of a minus and a dot in front of a number and different types of spelling are taken into account, but when comparing it is not accepted take into account the case of characters and the presence of an accent). Improved performance of UCA operations in utf8mb3 and utf8mb4 functions.
  • Implemented the ability to add IP addresses to the list of Galera Cluster nodes that are allowed to execute SST/IST requests.
  • By default, the "explicit_defaults_for_timestamp" mode is enabled to approximate the behavior to MySQL (the contents of DEFAULT blocks for the timestamp type are not shown when executing "SHOW CREATE TABLE").
  • In the command line interface, the "--ssl" option is enabled by default (establishing connections with TLS encryption is enabled).
  • The processing of top-level UPDATE and DELETE statements has been reworked.
  • The DES_ENCRYPT and DES_DECRYPT functions and the innodb_prefix_index_cluster_optimization variable have been deprecated.

Source: opennet.ru

Add a comment