Will Maria Live Up To The Hype?
Monty recently announced the Maria engine for MySQL, promising MVCC, better memory management, crash-safe design, and ACID compliance among other things. But will it live up to the hype? I’ve been disappointed in the past, mainly with InnoDB, so I’m understandably a bit skeptical that this will be a major leap for MySQL. I would much rather see better datatype integration, and things like dynamically generated default values fixed (try setting a default value to CURRENT_DATE(), you’ll see what I mean).
My biggest beef with MySQL is they never seem to fix things that do not work as they should. For example, if you do BEGIN; CREATE TABLE; ROLLBACK;, the table will still exist after the ROLLBACK command, and also, constraints are often completely ignored.
March 21st, 2008 at 1:16 pm
InnoDB transactions don’t work for any operation which changes table structure, so any ALTER/CREATE/DROP TABLE/INDEX statement is non-atomic.
You’re right to be skeptical. It seems that every problem MySQL has is solved with yet another storage engine. You end up with a profusion of engines, which are all centered around providing a specific feature, but often lack other features you want.