Release date: 16 Aug 2013
MariaDB 10.0 is the current development version of MariaDB. It is built on the MariaDB 5.5 series with backported and reimplemented features from MySQL 5.6 and entirely new features not found anywhere else.
MariaDB 10.0.4 is an Alpha release. This is the fifth 10.0-based release, and we are releasing it now to get it into the hands of any who might want to test it. Not all features planned for the MariaDB 10.0 series are included in this release. Additional features will be pushed in future releases. Do not use alpha releases on production systems.
Based on MariaDB 5.5
In most respects MariaDB will work exactly as MySQL: all commands, interfaces, libraries and APIs that exist in MySQL also exist in MariaDB.
This release includes fixes for the following security vulnerabilities:
Newly Implemented Features
- MDEV-4438 - Spider storage engine
- MDEV-4568 - Port Percona response time distribution as audit plugin
- MDEV-4702 - Reduce usage of LOCK_open
Features and Fixes Merged or Backported from MySQL 5.6.10
- MDEV-330 - Support for MySQL-5.6 created tables (frm and data files) that have columns of types TIME(N), DATETIME(N) and TIMESTAMP(N). Previously, an attempt to open such a table in MariaDB would return an error.
- MDEV-3838 - Support for standard SQL temporal literals
- MDEV-4058 - Merge the host_cache P_S table
- WL #5185 Remove deprecated 5.1 features
- InnoDB from MySQL 5.6.10
- Performance schema updates, including new defaults.
- Information Schema updates, including new defaults.
- InnoDB persistent statistics.
- Online ALTER for InnoDB and thread information for in-place operations
- EXCHANGE PARTITION
- Partition selection
- For temporary tables created with the
CREATE TEMPORARY TABLEstatement, the privilege model has changed (MySQL Bug #27480, Bug #11746602)
- GET DIAGNOSTICS statement
For full details, see the changelog.
CONNECT Storage Engine Updates
New features added to CONNECT
- The connection parameter of MYSQL type tables and PROXY tables on MySQL tables can now refer to a Federated server.
- The SERVID special column is now implemented. It returns the Federated server name for tables using one, the host name of the server for MYSQL tables, "ODBC" for ODBC tables and "Current" for all other table types. For PROXY and PROXY based tables, this value is the one of the source proxied table(s).
Modifications to CONNECT Behavior
- Table locking (read and write) is now supported. When a table is write locked, indexes are not updated on table changes. They are when the table is unlocked. Consequently, SELECT statements do not use indexing while locked.
- CONNECT no longers uses the query cache. This is because it is working on external data which is prone to be modified outside of MariaDB (it was also causing a crash with PIVOT tables)
Modifications to CONNECT Error messages
Some messages were changed from error to warning to prevent a server crash. Some have been added, in particular:
- When trying to index a null-able column (not supported yet)
- When inserting on an INI table without specifying the sectio name.
- When specifying ENUM column (not supported yet)
- Better message for CONNECT unspported commands
CONNECT Engine Bugs fixed:
A few bugs were fixed, in particular:
- MDEV-4494: Unsupported use of nullable column for index is not caught, causes assertion failure or unspecified error (122)
- MDEV-4495: Assertion failure in Diagnostics_area::set_error_status or unspecified error instead of a duplicate key error
- MDEV-4524: Server crashes when querying from multiple file CONNECT table
- MDEV-4638: Server crashes with an indexed not-null ENUM column
- MDEV-4771: Connection dies using table_type=pivot
- MDEV-4853: DML on table_type=INI gives no error even MySQLd has not the privilege to change the file
- MDEV-4854: table_type=mysql does not send the WHERE part (not a bug)
- MDEV-4855: If SERVID is not supported, it should be removed from doc.
- MDEV-4878: LOCK TABLE is not working with ConnectSE
- MDEV-4881: Pivot throws an error
- Fixed a bug causing the whole section to be deleted when deleting one key of a INI table with layout=Row. The same happens for layout=column but this is normal as one line is one section.
- Fixed a bug causing connect_assisted_discovery to fail on some table types (WMI).
- A fix concerning a memory leak or uninitialised memory warning issued by Valgrind.
- A few more code changes have been made to suppress compilation warnings.
Thanks, and enjoy MariaDB!