MariaDB Server is a database server. MariaDB turns data into structured information in a wide array of applications, ranging from banking to websites. It is an enhanced, drop-in replacement for MySQL. MariaDB is used because it is fast, scalable and robust, with a rich ecosystem of storage engines, plugins and many other tools make it very versatile for a wide variety of use cases.
MariaDB is developed as open source software and as a relational database it provides an SQL interface for accessing data. The latest versions of MariaDB also include GIS and JSON features.
v5.5 [Apr 28, 2012]
- tweak the test to pass, until the upstream MySQL Bug #61209 is completely fixed
- Fixed Bug #972973
- When the function free_tmp_table deletes the handler object for a temporary table the field TABLE::file for this table should be set to NULL. Otherwise an assertion failure may occur.
- Fixed Bug #915222. This bug happened because the function find_field_in_view formed autogenerated names of view columns without a possibility to roll them back. In some situation it could cause memory misuses reported by valgrind or even crashes.
- Unused method removed.
- mdev-80 Memory engine table full at much less than max_heap_table_size with btree index.
- RB-tree index in the MEMORY table fails if it grews over 4G.
- That happened because the old_allocated variable in hp_rb_write_key() had the uint type. Changed with the 'size_t' type to be same as the 'rb_tree.allocated'.
- Memory engine table full at much less than max_heap_table_size with btree index.
- don't cast implicitly an int to a char, when a boolean value is desired.
- fix of Bug #968720.When a view/derived table is converted from merged to materialized the items from the used_item lists are substituted for items referring to the fields of the result of the materialization. The problem appeared with queries employing natural joins. Since the resolution of a natural join was performed only once the used_item list formed at the second execution of the query lacked the references to the fields that were used only in the equality predicates generated for the natural join.
- Fixed additional changed pbxt test cases
- Merge in deleted fixes
- Fixed test cases that changed as part of fixing bugs with record count and partitioning
- better comments and function names.
- Bug #913030: Optimizer chooses a suboptimal excution plan for Q18 from DBT-3
- When doing join optimization, pre-sort the tables so that they mimic the execution order we've had with 'semijoin=off'.
- That way, we will not get regressions when there are two query plans (the old and the new) that have indentical costs but different execution times (because of factors that the optimizer was not able to take into account).
- Fixed Bug #944422 "mysql_upgrade destroys Maria tables?" The issue was that check/optimize/anaylze did not zerofill the table before they started to work on it.
- Added one more element to not often used function handler::auto_repair() to allow handler to decide when to auto repair.
- Added a --nowatch (with aliases --no-watch and --no-auto-restart) option to mysqld_safe that causes it to exit after spawning mysqld.
- Windows threadpool - always disassociate current thread from callback when destroying connection prior to closing callbacks and calling DestroyThreadpoolEnvironment, to make sure callbacks do not wait for themselves to finish.
Feature-rich relational database known for its high performance and excellent concurrency
