Hello.
Put SET FOREIGN_KEY_CHECKS=0 at the top of your dump file. In 4.1, mysqldump puts that automatically to the dump file. See comments at: http://dev.mysql.com/doc/mysql/en/mysqldump.html Michael Satterwhite <[EMAIL PROTECTED]> wrote: > mysqldump backs all of the tables up in alphabetic order, including the > table create statements. The problem is that if foreign keys exist on > the tables, the reload will not work unless the backup file is hand > edited to insure that tables depended upon are created first. Is there a > way around this? If not, shouldn't the tables be created first and the > foreign keys created at the end of the backup? I *REALLY don't want to > hack mysqldump and am hoping that there's already a way around this - or > that a way is being developed. > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
