Bug #17950 Table storage types get lost in migration
Submitted: 6 Mar 2006 5:01 Modified: 12 Jun 2006 19:32
Reporter: Craig Williams Email Updates:
Status: Closed Impact on me:
Category:MySQL Migration Toolkit Severity:S2 (Serious)
Version:.23rc OS:Windows (Windows XP SP2)
Assigned to: Michael G. Zinner CPU Architecture:Any

[6 Mar 2006 5:01] Craig Williams
I was migration data from a MySQL 5.x database to a MySQL 4.x database. I had several tables set with a storage type of MyISAM. The migrated tables were changed to InnoDB.

How to repeat:
Create a table in the Source server and set its storage to MyISAM.
Migrate this table to another MySQL database. Notice how the table storage changes to InnoDB.

Suggested fix:
I believe the storage type should not be changed during migration.
[7 Mar 2006 23:09] MySQL Verification Team
Thank you for the bug report. I was unable to find an option in the
Object Mapping which permits to migrate a mixed  storage engines
tables according how were created originally.
[12 Jun 2006 19:32] Michael G. Zinner
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 bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

In the next release the following workflow will preserve the table engine type.

On the Object Mapping page, click the [Set Parameter >>] button, select [X] User defined and make sure to remove "engine" from the parameter list or leave it empty. 

Example: addAutoincrement=yes, charset=utf8, collation=utf8_general_ci, engine=

This will preserve the original table type.