MySQL Bugs: #37827: Migration tool doesn't allow transform

Bug #37827	Migration tool doesn't allow transform
Submitted:	2 Jul 2008 22:46	Modified:	14 May 2009 12:39
Reporter:	Luís Ferro	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Migration Toolkit	Severity:	S4 (Feature request)
Version:	1.1.12	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	Logs, transform, warnings

Description:
When using the migration tool, it doesn't allow for the data transform, not only within the same table, but also join/split tables apart.

This will allow only for 1-1 migration mode.

For instance, a table of locals with:

code         varchar(5)
description  varchar(200)
country     varchar(50)

Should be if interested be migrable to:

locals -> id [primary], code [unique index], description [=], country [foreign key id]

countries -> id [primary], country [=]

Currently, this is impossible.

The target mysql database isn't asked and is assumed to be the same as the origin. This is incorrect. After asking for the source database, it should be asked the target one.

Manual editing step doesn't allow to edit anything (one would suppose that it would allow to twick the whole migration objects).

Either redefine the step with another name (like view migration objects), or implement the editing as the name implies.

Creation results aren't neither editable nor viewable.

How to repeat:
Open the migration tool and add a connection for both the source and target to point to the same server.

Select one database.

Try to migrate it to a diferent database.

The tool assumes that the target is equal to the source.

It doesn't migrate anything and doesn't even provide a warning about it.

Doesn't log the steps.

Suggested fix:
Implement data join/split where several tables can be joined together and then split with differently organized table structure.

Many thanks for writing a feature request. This isn't not easy to implement. Anyway I will give it to development for discussion.

Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Migration Tool into MySQL Workbench. We won't add this feature request anymore.

More informations about MySQL Workbench you will find here:

http://dev.mysql.com/workbench/