MySQL Migration problem with enums

I was testing the MySQL Migration process and I ran into an issue with columns that are defined as enum in MySQL. While Postgres doesn't support the enum type, it does offer two equivalents via custom data types and CHECK constraints. I tried using the Migration tool two ways.

1) Migrate both the schema and data from a MySQL table with an enum column to a clean Postgres database. Migration failed with an error about the enum column.

2) Create the table in Postgres and define the enum column as varchar with a CHECK constraint. Migrate just the data from MySQL to the empty table in Postgres. Migration failed with the same error.

Am I doing something wrong? Is this a known issue? Other than ALTERing the MySQL tables that use enum columns, are there other workarounds?

Any advice would be greatly appreciated! Thanks.

-Sean

You followed the right steps, however currently the "enum" mapping is not being handled by MTK. I have forwarded this case to our development team and will get back to inform about the future release or a quick hot fix (in which you will simply have to download the MTK distro through EnterpriseDB Update service and it'll replace the existing jar on your system) availability to take care of this problem.

Thanks,
Zahid

A correction, the Update Service is not applicable to Migration Wizard, we'll send the details once the updated version of Migration Wizard is available.

Thanks,
Zahid

What you could also do is use an open source ETL tool. They are free to download.

Talend Open Studio is an open source ETL tool for data integration and migration experts. It's easy to learn for a non-technical user. What distinguishes Talend, when it comes to business users, is the tMap component. It allows the user to get a graphical and functional view of integration processes.
For more information: http://www.talend.com/

Sean_L wrote:I was testing the MySQL Migration process and I ran into an issue with columns that are defined as enum in MySQL. While Postgres doesn't support the enum type, it does offer two equivalents via custom data types and CHECK constraints. I tried using the Migration tool two ways.

1) Migrate both the schema and data from a MySQL table with an enum column to a clean Postgres database. Migration failed with an error about the enum column.

2) Create the table in Postgres and define the enum column as varchar with a CHECK constraint. Migrate just the data from MySQL to the empty table in Postgres. Migration failed with the same error.

Am I doing something wrong? Is this a known issue? Other than ALTERing the MySQL tables that use enum columns, are there other workarounds?

Any advice would be greatly appreciated! Thanks.

-Sean

Hi Sean
I have completed step 3 but stuck in the 4th step (Source Schema) to migrate from mysql to postres. could you please tell me what should I give the value here?
-Provas