Re: Foreign Keys in CREATE TABLEs produced by mysqldump

2003-12-30 Thread Heikki Tuuri
Michael, - Alkuperäinen viesti - Lähettäjä: <[EMAIL PROTECTED]> Vastaanottaja: "Heikki Tuuri" <[EMAIL PROTECTED]> Kopio: <[EMAIL PROTECTED]> Lähetetty: Monday, December 29, 2003 11:53 PM Aihe: Re: Foreign Keys in CREATE TABLEs produced by mysqldump > &

Re: Foreign Keys in CREATE TABLEs produced by mysqldump

2003-12-29 Thread michael_muir
"Heikki Tuuri" <[EMAIL PROTECTED]> wrote on 12/24/2003 01:53:07 PM: > Michael, > > this is the question where the valid answer is: upgrade! > In which version was this corrected? I'm hesitant to upgrade to the latest and greatest without it being banged on by the masses first.. I have half a d

Re: Foreign Keys in CREATE TABLEs produced by mysqldump

2003-12-24 Thread Heikki Tuuri
Michael, - Original Message - From: <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Wednesday, December 24, 2003 1:45 AM Subject: Foreign Keys in CREATE TABLEs produced by mysqldump > --=_alternative 008277CD88256E05_= > Content-Type: text/plain; chars

Foreign Keys in CREATE TABLEs produced by mysqldump

2003-12-23 Thread michael_muir
First let me state that this is not a question where a valid answer is to SET FOREIGN_KEY_CHECKS=0... (no, its not *that* question..) I have noticed that mysqldump includes the database name in foreign key specifications within CREATE TABLEs. This is causing a bit of grief as I would like to re