Bug #50551 MySQL Migration Toolkit problem with multiple schemas

• Submitted: 22 Jan 2010 17:04
• Modified: 22 Jan 2010 17:20
• Reporter: Diogo Rafael Jacobs
• Status: Unsupported
• Category: MySQL Migration Toolkit
• Severity: S3 (Non-critical)
• OS: Any
• CPU Architecture: Any
• Tags: MSSQL Server, MySql Migration toolKit

[22 Jan 2010 17:04] Diogo Rafael Jacobs

Description:
Hi Guys,

First of all congratulations for the MySQL Migration Toolkit application, it is a great solution.

My bug report is about a problem that I've found when migrating from a MSSQL Server database, the fact is, when we have tables with the same name, in diferent schemas, lets imagine:

schema1.user (
 id int not null,
 email varchar(50) not null
)

schema2.user (
 id int not null,
 email varchar(50) not null
)

The resulting migration script will be:

create table user(
id int not null,
id int not null,
email varchar(50) not null,
email varchar(50) not null
) 

and the data migration script will be:
insert into user (id,id,email,email) .... and so one 

I've renamed the table in schema2 to user123, and tried the whole process again, and it worked just fine.

Could you please check?

Tnks!

How to repeat:
Create the table structure above, and try your self.

After renaming the table from the discarded schema, things will work just fine.

Suggested fix:
When you describe table meta data, tou should take care the schema name, in order to have only the columns of the table from the desired schema.

[22 Jan 2010 17:20] Valeriy Kravchuk

Migration Toolkit bug fixing is stopped for some time already. Read http://www.mysql.com/support/eol-notice.html, message dated December 18, 2009.