SQL Server Migration To Refactored MySQL w/ InnoDB Key & Constraint Issues -
I am redeveloping a web application and originally based on SQL Server 2005, ASP.NET & For a Windows 2003 LAMMP (Extra M for the Mkcch course) and since the schema is heavy rebuilt (with a great reason to do so) I should write a custom migration app
The problem is the InnoDB Primary + Foreign key barriers have hindered my ability to insert data into my MySQL / InnoDB tables. I have tried to use the disable key and I already have it; By deleting the FOREIGN_KEY_CHECKS methods and temporarily removing auto-increments on the primary, it throws an error when trying to change either of these, such as the abnormal keys, because it is unsupported in the InnoDB or the primary in any column Attempting to remove key assignment throws errors in the empty table or migration app that says the record is empty when the table is empty When the key is already present, is there anything else that can be done before, except before removing all things and returning it later (which I think will give me hell too)?
Thank you!
>
triggers this task:
ALTER TABLE `site_oltp Modify `.members` COLUMN` id` INT (11) No; Set FOREIGN_KEY_CHECKS = 0, UNIQUE_CHECKS = 0;
Enter the records ....
Alternate table `site_typ` .mix 'column' id 'INT modify (11) null atrangement; Optional table `site_typ` 'Mailers' AUTO_INCREMENT = (LAST_ID_GOES_HERE + 1); SET FOREIGN_KEY_CHECKS = 1, UNIQUE_CHECKS = 1 ";
Comments
Post a Comment