So, as a followup, I ran mysqldump on the actual server (with the output
directed over AFP to another machine on the network) -- as opposed to running
mysqldump on the destination server and connecting to the databases over TCP/IP
(both are running 5.1.39 PPC 64-bit). *That* dump file imported
It's just odd, because that error was on 5.0. I'm running 5.1.39 -- surely
enough time for the MySQL devs to fix it right?
Could it be with extended inserts that the max statement length is greater than
the default 16MB max allowed packet? I'm increasing that value to 256 MB and
going to try
There is a bug in mysqldump that prevents mysql from version 5.0.80 from
importing dumps from a old version of mysqldump.
I had this verified by MySQL support.
You can have a look at this bug: http://bugs.mysql.com/bug.php?id=41486
Cheers
Claudio
2009/11/21 René Fournier m...@renefournier.com
Except that, in my case, both machines are running 5.1.39. Mac OS X PPC
64-bit. I tried importing another, different dump file of the same database,
and this time mysql returned a different error:
Sat Nov 21 13:16:20 -- Minas-Tirith :: mysql -u root -p dump_file.sql
Enter password:
ERROR
Have you tried dumping that table manually using mysqldump on the command line
to confirm it's not an issue with automysqlbackup?
Regards,
Gavin Towey
-Original Message-
From: René Fournier [mailto:m...@renefournier.com]
Sent: Friday, November 20, 2009 8:31 AM
To: mysql
Subject: Strange
Yes, still exhibits this problem -- although at a different line in the file.
(Seems random.) I should also mention, the backup is running across a local
network. The machine the starts automysqlbackup (and internally, mysqldump)
connects over TCP/IP to the database server. I am going to try
