Bug #19775 Incorrect foreign key contraint action in Schema Creation from SQL Server
Submitted: 12 May 2006 16:14 Modified: 22 Jun 2006 13:43
Reporter: Andrew Timberlake-Newell Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S3 (Non-critical)
Version:1.0.25 OS:Windows (Windows XP SP2)
Assigned to: Michael G. Zinner CPU Architecture:Any

[12 May 2006 16:14] Andrew Timberlake-Newell 
Description:
Foreign Key ON UPDATE CASCADE in SQL Server 2005 gets generated as ON UPDATE NO ACTION in Schema Creation step.

How to repeat:
SQL Server syntax to add foreign key:

ALTER TABLE [dbo].[SecondTable]  WITH CHECK ADD  CONSTRAINT [FK_SecondTable_FirstTable] FOREIGN KEY([SomeID])
REFERENCES [dbo].[FirstTable] ([ID])
ON UPDATE CASCADE

MT generated constraint portion of CREATE TABLE:

  CONSTRAINT `FK_SecondTable_FirstTable` FOREIGN KEY `FK_SecondTable_FirstTable` (`SomeID`)
    REFERENCES `TestDB_dbo`.`FirstTable` (`ID`)
    ON DELETE NO ACTION
    ON UPDATE NO ACTION
[25 May 2006 15:13] Jorge del Conde 
Thanks for your bug report.  I was able to reporduce this with XP64/MSSQL2005
[22 Jun 2006 13:43] 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
    http://www.mysql.com/doc/en/Installing_source_tree.html