From: Sinisa Milivojevic Date: February 26 2004 3:04pm Subject: Re: Bug in new FOREIGN KEY checks in MySQLInnoDB/4.0.18 List-Archive: http://lists.mysql.com/bugs/15259 Message-Id: <16446.2808.830946.151082@sinisa.nasamreza.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Steve Hay writes: > Sinisa Milivojevic wrote: > I understand that if I was issuing DROP TABLE statements then I would > need to put them in the right order, but I'm doing a DROP DATABASE. > > Surely foreign key constraints should not be checked when the entire > database is being dropped. > > If they /are/ supposed to be checked then the other cases that I > mentioned above (where DROP DATABASE worked fine) are not working properly! > > - Steve > Just as our manual says, drop tables one by one, as foreign constraints need be constrained to a single database. -- Sincerely, -- For technical support contracts, go to https://order.mysql.com/?ref=msmi __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic / /|_/ / // /\ \/ /_/ / /__ MySQL AB /_/ /_/\_, /___/\___\_\___/ Full time Developer and Support Coordinator <___/ www.mysql.com Larnaca, Cyprus Meet the MySQL at User Conference ! (April 14-16, 2004) http://www.mysql.com/uc2004/