MySQL storage engine woes

Friday, December 23rd, 2005

Are you suffering from mysteriously failing insert queries due to foreign key constraints errors in MySQL?

Have you noticed spontaneous table storage engine changes from InnoDB to MyISAM, but can’t figure out why they’re happening?

You may be coming under the influence of the MySQL Command Center which, when altering a table via the Edit table interface, doesn’t load the correct table type in the type dropdown, but defaults to MyISAM. This causes each table change you make to revert the table to MyISAM if no foreign key constraints are present in the table. Otherwise, the edit simply fails.

When editing a table, check the ‘Table properties’ tab before saving your changes. It’ll save you a lot of headaches.