Bug #20369 Unable to set InnoDB as default engine
Submitted: 9 Jun 2006 21:29 Modified: 28 Jul 2006 5:02
Reporter: Moreno Trinca Email Updates:
Status: Closed Impact on me:
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.1.10-1 OS:Linux (Mandriva 2006.0)
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: Server Configuration

[9 Jun 2006 21:29] Moreno Trinca
I set default-storage-engine=innodb parameter in my.cnf; if I create a new table with mysql-client, without storage engine specifycation, I get an InnoDb table. However when I try to create a table with mysql-administrator it's created with MyISAM storage engine: in fact when I'm defining the table, if I check "Table option" tab in table editor I can recognize by the *description* that MyISAM storage engine is set as default (the combo box with the name of storage engine is empty... and so is the list where to choose the engine from, but if I click on the list I can see the storage engine description change! ).
I faced this problem also in mysql-administrator 1.1.6 on Fedora Core 5. On this version "table option" tab layout is quite different but the default storage engine is still MyISAM and you have to manually change it before creating te table if you wanto to get an InnoDB table.
MySQL server version: MySQL-max 5.0.22
InnoDB is enabled (skip-innodb option not set)

How to repeat:
Set default-storage-engine=innodb in my.cnf (either editing it directly or by mean of mysq-administrator), restart the server, then using mysql-administrator try to create a new table, without changing the storage engine in "table option" tab of Table editor. Check if the new table is an InnoDb or MyISAM table
[14 Jun 2006 15:59] MySQL Verification Team
Thank you for the bug report. Tested on Suse 10.
[28 Jul 2006 5:02] Alfredo Kojima
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at