Re: Foreign Keys in CREATE TABLEs produced by mysqldump

"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: Strange performance problem importing dumped data (3.23.58 on FreeBSD 5.2-RC1)

I have found that by dumping with --extended-insert, the subsequent import is MUCH faster. Of course it only issues 450 odd queries for the data set instead of ~200k... -mike [EMAIL PROTECTED] 12/23/03 05:02 PM To [EMAIL PROTECTED] cc Subject Strange performance problem importing dump

Strange performance problem importing dumped data (3.23.58 on FreeBSD 5.2-RC1)

I am using 3.23.58 (server and client) on FreeBSD 5.2-RC1 and all of what I am about to describe is being performed locally. When importing dumped data (with something like mysql dbname < dbname.dump) the import is being performed at ~60 queries a second. This is MUCH slower than when I was run

Foreign Keys in CREATE TABLEs produced by mysqldump

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