Bug #11099 | Bug selecting wrang primary keys.... | ||
---|---|---|---|
Submitted: | 4 Jun 2005 17:44 | Modified: | 26 Oct 2005 21:51 |
Reporter: | Peter Fassev | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Migration Toolkit | Severity: | S2 (Serious) |
Version: | OS: | Windows (Win 2000, SQL Server 2000) | |
Assigned to: | CPU Architecture: | Any |
[4 Jun 2005 17:44]
Peter Fassev
[20 Jun 2005 18:18]
Marc Hale
i get the same error if the Primary Key is not the first column it makes whatever is in the first column the primary key. also during the migration if it get an error creating a table it does not tell you. and when it trys to import the data it just hangs because table does not exist.
[25 Jun 2005 16:13]
Jorge del Conde
Hi! Thanks for your bug report. I was able to reproduce this bug using the supplied information.
[19 Oct 2005 17:02]
Michael G. Zinner
Jorge, could you see if this bug is still existing in the latest release? I tested with if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[test2]') and OBJECTPROPERTY(id, N'IsUserTable') = 1) drop table [dbo].[test2] GO CREATE TABLE [dbo].[test2] ( [test1] [int] NULL , [test2] [int] NOT NULL , [test3] [int] NULL , [test4] [int] NOT NULL ) ON [PRIMARY] GO ALTER TABLE [dbo].[test2] WITH NOCHECK ADD CONSTRAINT [PK_test2] PRIMARY KEY CLUSTERED ( [test2], [test4] ) ON [PRIMARY] GO which produced CREATE TABLE `Northwind_dbo`.`test2` ( `test1` INT(10) NULL, `test2` INT(10) NOT NULL, `test3` INT(10) NULL, `test4` INT(10) NOT NULL, PRIMARY KEY (`test2`, `test4`) ) ENGINE = INNODB; and that is correct.
[26 Oct 2005 21:51]
Jorge del Conde
I was unalbe to reporoduce this bug using the lasest version of MT