The first stable release of the new branch of the MariaDB database management system 10.10 (10.10.2) has been published. This branch develops a fork of MySQL, maintaining backward compatibility while integrating additional storage engines and extended capabilities. The development of MariaDB is overseen by the independent organization MariaDB Foundation, following an open and transparent development process, independent of individual vendors. MariaDB replaces 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.
Key improvements in MariaDB 10.10:
- The RANDOM_BYTES function has been added to obtain a random sequence of bytes of a specified size.
- The INET4 data type has been added to store IPv4 addresses in a 4-byte representation.
- The default parameters for the 'CHANGE MASTER TO' statement have been changed to use GTID-based replication mode (Global Transaction ID) if the master server supports this type of identifier. The setting 'MASTER_USE_GTID=Current_Pos' is deprecated and replaced by the 'MASTER_DEMOTE_TO_SLAVE' option.
- Merge optimizations with a large number of tables have been expanded, including the possibility of using 'eq_ref' for merging tables in any order.
- UCA (Unicode Collation Algorithm) has been implemented as defined in the Unicode 14 specification, used for defining sorting and matching rules that consider the meaning of characters (for example, when sorting numeric values, the presence of a minus sign and point before the number and different writing styles are taken into account, while case sensitivity and accents are ignored in comparisons). The performance of UCA operations in utf8mb3 and utf8mb4 functions has been improved.
- The ability to add (the key to connect to is specified, and iroh finds the associated host and establishes an encrypted connection using the QUIC protocol). Direct P2P connections are established whenever possible, but if not, it falls back to using relays, which are also employed for host discovery by keys. You can run your own relay or connect to public relays supported by the community. to the list of Galera Cluster nodes allowed to execute SST/IST queries has been implemented.
- By default, the 'explicit_defaults_for_timestamp' mode is activated to bring behavior closer to MySQL (the contents of the DEFAULT blocks for the timestamp type are not shown when executing 'SHOW CREATE TABLE').
- In the command line interface, the '—ssloption is enabled by default (TLS encryption for connections is enabled).
- The processing of top-level UPDATE and DELETE statements has been redesigned.
- The functions DES_ENCRYPT and DES_DECRYPT, as well as the variable innodb_prefix_index_cluster_optimization, have been deprecated.
Source: opennet.ru
