MariaDB 10 adds in many major features that I will talk about in this course, including global transaction IDs and multisource replication. MariaDB version 10.0 has all of the features of MariaDB version 5.5 but adds in some of the MySQL 5.6 features. Newer versions of MariaDB are numbered starting with 10. So for the next version, MariaDB decided to change the numbering altogether, so there would not be any confusion. Calling it 5.5 is confusing because naturally we would think it has all the features of MySQL 5.5, but it does not. Not all the MySQL 5.5 features are being put into MariaDB 5.5, and there are extra features from the previous MariaDB releases. But we are now seeing a problem with the version numbering. Most of the major features were optimizations that I will not explain. MariaDB 5.5 is based on MariaDB 5.3 but adds in many of the MySQL 5.5 features. For more information about dynamic columns, see the course called Understanding MariaDB for MySQL Users here on. Another feature MariaDB added in 5.3 is dynamic columns. MariaDB 5.3 also adds geographic information systems features, or GIS features. I will also explain the HandlerSocket plugin, which is a plugin that works on both MySQL and MariaDB. In this course, I will be going over the progress reports in PROCESSLIST and microsecond precision in time data types. The major features in MariaDB 5.3 include several optimizations, subquery optimizations and join optimizations. MariaDB 5.3 has everything in MariaDB 5.2, which means it is also based on MySQL 5.1. There are other major features in MariaDB 5.2 that I will discuss later, including virtual columns, user statistics, and the authentication plugin. Like the Federated, PBXT, and XtraDB storage engines, the OQGraph and Sphinx storage engines can be added on to standard MySQL but are packaged alongside MariaDB. In addition, they packaged the Open Query Graph storage engine and the Sphinx storage engine for better full-text searches. MariaDB 5.2 is still based on MySQL 5.1, and contains all of the features of MariaDB 5.1. They did the same for MariaDB 5.3, adding features that are not in MariaDB 5.2. Instead of having the major features added to MariaDB 5.1, they created a MariaDB 5.2 release. MariaDB, however, decided to add more major features. MySQL skipped right from version 5.1 to 5.5. They are server thread pooling, which makes the database system more scalable, and microsecond precision in the PROCESSLIST. There were two other features added in MariaDB 5.1 which I will talk about in more detail a little later. Aria is faster for these internal temporary tables, so even early on in MariaDB 5.1 a performance difference could be noticed. Aria is used for internal temporary tables which use MyISAM and MySQL. However, there are information schema tables in MariaDB that use the Aria storage engine. Right now, system tables in MariaDB still use the MyISAM storage engine. It is crash-safe and currently non-transactional. The Aria storage engine was developed to be a better MyISAM storage engine and eventually replace it. The biggest change was the implementation of the Aria storage engine. The XtraDB, PBXT, and FederatedX storage engines were available as add-ons to MySQL, but MariaDB shipped these storage engines with the regular database server. For example, MariaDB came with more storage engines. The first version of MariaDB to come out was 5.1, and it was based on MySQL 5.1. MariaDB is a fork of MySQL created by one of the original founders of MySQL.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |