Bug #27630 Mysql Migration Toolkit... Foreign and Primary Keys lost in process...
Submitted: 3 Apr 2007 23:52 Modified: 24 Oct 2007 6:12
Reporter: Jeremy Brown Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Migration Toolkit Severity:S4 (Feature request)
Version:version 1.1.10 OS:Windows (WinXP)
Assigned to: CPU Architecture:Any

[3 Apr 2007 23:52] Jeremy Brown 
Description:
I don't know if this is a bug, or just my own stupidity but it would be very useful to be able to select a foreign key migration method other than general...

In migrating tables you have the option to select a detailed migration method... this includes the type of migration for foreign keys...  Now the only method shown is "General" or you can choose custom and write your own code to migrate the information with...  I'm not an experienced mysql person so when i found the gui kit and migration tool it made my life a million times easier...  But one thing i've noticed is that the foreign keys don't show up when i finish a migration... I don't know if its the way i set it up, or what, but if there was another selection there for type of foreign key and primary key migration possibly to make it work better that would be greatly appreciated...  If this isn't the problem I'm sorry for my inexperience with the system, but if it is I hope I've helped...

And thank you so much for all the work you've done so far with the migration toolkit and all the gui tools put out to the open market not to mention MySQL as a whole...  to be free and very useful so that everyone can use it...
Thx again and i look forward to future releases you may be working on...

Have a great day :),

  ~C_elite
  admin@ficsmypc.com
  kid1_1kid@yahoo.com
  yahoo ID: kid1_1kid

How to repeat:
do a mysql migration on innoDB tables and db and select defaults for migration methods
[24 Sep 2007 6:12] Valeriy Kravchuk 
Thank you for a feature request. Please, check with a newer version, 1.1.12, and inform about the results.
[24 Oct 2007 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".