Talk:Comparison of MySQL database engines

[Untitled]

 * 1) POV - Complaints regarding the neutrality of this content began on the pages for InnoDB and MyISAM which lead to the creation of this article. SloppyG (talk) 16:24, 8 October 2011 (UTC)
 * 2) What about Mariadb? it has many new engines

Bias towards MyISAM
This article seems highly biased against MyISAM and reads like an advert for InnoDB! Lacks real credibility. — Preceding unsigned comment added by 94.175.81.139 (talk) 00:56, 25 October 2011 (UTC)
 * I agree, it's not very well-written. However, I applaud SloppyG for starting the fixing process by moving these bullets to a central location from where they were before.
 * I think it would be a good idea to turn this into an actual table of storage engine features, with some detailed description of some of the more finer differences above/below the table. Whenever someone gets the chance. ~ Josh "Duff Man" (talk) 05:06, 25 October 2011 (UTC)
 * Perhaps the above comments are dated. There is no apparent bias.  In professional relational DB circles InnoDB is strongly preferred.  Indeed most relational database systems do not offer an engine that is less capable of full ACID.  The article is well written and to the point.  Perhaps someone that has a really great use case or two for MyISAM can add to it.  Personally I have yet to find a case where it is the right choice.  — Preceding unsigned comment added by Sjatkins (talk • contribs) 20:49, 2 May 2017 (UTC)

Proposals to modify the table
I propose some changes to the storage engines table. I can make the changes myself if they're approved. --81.98.53.246 (talk) 10:58, 13 November 2020 (UTC)
 * Move obsolete engines to another table, with its own title. So we don't pollute information about the currently supported engines.
 * We could add columns "MySQL versions" and "MariaDB versions". Content example: "5.0-5.5". in this way it will be clear if the engine is still available, and when it was first made available.
 * If the previous proposal is accepted, please let's remove "actively developed". For example, FEDERATED may not be actively developed but it's shipped with both MySQL and MariaDB. MyISAM is not actively developed since the Stone Age, except for some additions made by MariaDB in the Middle Age.
 * We could add a column "Description". It should contain a single statement about the engine. When it makes sense, it should be copied from the output of the SHOW ENGINES command. Where the command doesn't provide a meaningful description (for example, for MyISAM is just says "MyISAM storage engine", which means nothing) we can describe the engine in the shortest possible way.
 * I am the author of the previous comment. I think I wasn't logged in. --Federico Razzoli (talk) 00:26, 14 November 2020 (UTC)
 * Sounds good to me. Greenman (talk) 17:34, 13 November 2020 (UTC)