Bob, thank you!
I believe 3.23.50 will be out in two weeks. It is a stable version. The changes in foreign keys were actually rather small. I hope they do not degrade .50 to the beta category. Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ Speed up adding of features to MySQL/InnoDB through support contracts See http://www.innodb.com for the online manual and latest news on InnoDB -----Original Message----- From: Bob McLaughlin <[EMAIL PROTECTED]> To: Heikki Tuuri <[EMAIL PROTECTED]>; MySQL Mailing List <[EMAIL PROTECTED]> Date: Tuesday, March 12, 2002 4:00 PM Subject: RE: Foreign keys in mysqldump? >Heikki, > >You are the man! > >I am glad you are addressing these issues in 3.23.50. They will make >foreign key support in MySQL much more robust (in my opinion, anyway..) > >Is the .50 release available yet? If not, do you have a timeline for when it >will be, and when it would be recommended to use in production work? > >Thanks much, >-Bob > > >-----Original Message----- >From: Heikki Tuuri [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, March 12, 2002 4:50 AM >To: Bob McLaughlin; MySQL Mailing List >Subject: Re: Foreign keys in mysqldump? > > >Bob, > >I have now improved foreign key support so that version 3.23.50 does > >1. show the FOREIGN KEY definitions when you call SHOW CREATE TABLE; this >should also show them in mysqldumps; >2. preserve FOREIGN KEY definitions in ALTER TABLE and CREATE INDEX; >3. allow backquotes around column and table names in foreign key >definitions: backquotes are produced by SHOW CREATE TABLE; >4. allow adding a new foreign key constraint ot a table through > ALTER TABLE ... ADD CONSTRAINT FOREIGN KEY (...) REFERENCES ... (...); >remember though that you first have to create the appropriate indexes on the >parent and child table so that InnoDB approves the constraint. > >I try to get also in .50 a command SET FOREIGN KEY CONSTRAINT CHECKS=0 which >allows you to disable them when you import dumped tables in a wrong order >regarding to the foreign key definitions. > >In versions < 3.23.50 the only way to 'dump' foreign key definitions is to >call SHOW TABLE STATUS FROM ... which prints them in the table comments. > >Best regards, > >Heikki Tuuri >Innobase Oy >--- >Order technical MySQL/InnoDB support at https://order.mysql.com/ >Speed up adding of features to MySQL/InnoDB through support contracts >See http://www.innodb.com for the online manual and latest news on InnoDB > > >-----Original Message----- >From: Bob McLaughlin <[EMAIL PROTECTED]> >To: MySQL Mailing List <[EMAIL PROTECTED]> >Cc: Heikki Tuuri <[EMAIL PROTECTED]> >Date: Monday, March 11, 2002 8:11 PM >Subject: Foreign keys in mysqldump? > > >> >>When I do a mysqldump and include table creation, it does not seem to >>include the foreign key constraints in the create table statements of the >>InnoDB tables. >> >>Is there a command line switch or other way to make this happen? >> >>Thanks, >>-Bob > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
