Bug #62903 Workbench uses wrong name for MariaDB engine (Aria)
Submitted: 24 Oct 2011 1:38 Modified: 27 Jul 2012 8:33
Reporter: Yehuda Katz Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2.35 CE r7915 OS:Any
Assigned to: CPU Architecture:Any

[24 Oct 2011 1:38] Yehuda Katz
Workbench allows you to work with tables set to ENGINE=MariaDB, but the MariaDB engine was renamed to Aria in 2010, so the MariaDB engine is no longer recognized.

How to repeat:
Set a table to use the MariaDB engine and it will not be forward engineered.
Reverse engineer a database from MariaDB with tables using Aria and they will not be properly imported.

Suggested fix:
"%INSTALL_PATH%\MySQL Workbench 5.2 CE\modules\data\mysql_engines.xml"
> Change MariaDB to Aria (around line 170)

Alternatively, add Aria as another engine so that Workbench can be compatible with the few early releases that used that name.
[24 Oct 2011 3:34] Valeriy Kravchuk
Thank you for the problem report.
[27 Jul 2012 8:33] Philip Olson
Fixed as of Workbench 5.2.41, and here's the changelog entry:

"MariaDB" has been change to "Aria" within MySQL Workbench.