From: Claudio Nanni
Date: November 22 2009 12:05am
Subject: Re: Strange problem with mysqldump / automysqlbackup (ERROR 1300)
List-Archive: http://lists.mysql.com/mysql/219446
Message-Id: <53bcf3a60911211605k3f45a697n2875e004e27ff19f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=001485f8d1828e1f820478ea777c

--001485f8d1828e1f820478ea777c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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=3D41486

Cheers

Claudio



2009/11/21 Ren=C3=A9 Fournier <m5@stripped>

> It's just odd, because that error was on 5.0. I'm running 5.1.39 -- surel=
y
> enough time for the MySQL devs to fix it right?
>
> Could it be with extended inserts that the max statement length is greate=
r
> than the default 16MB max allowed packet? I'm increasing that value to 25=
6
> MB and going to try again.
>
> Thanks for the idea though. At least I'm not the only one to have
> encountered that error.
>
> ...Rene
>
> On 2009-11-21, at 5:44 AM, =E7=8E=8B=E6=B5=A9 wrote:
>
> > i googled the problem,it says that's a mysql bug.This is the source pag=
e
> :http://www.shinguz.ch/MySQL/mysql_trouble_shooting.html#backup_restore,
> > And i suggest you ignore the error when import or correct the dump to t=
he
> source database and then import again.
> >
> > Best wishes!
>
>


--=20
Claudio

--001485f8d1828e1f820478ea777c--