Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: René Fournier (m5renefournier.com)
Date: Sat Nov 21 2009 - 15:14:14 CST
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 again.
Thanks for the idea though. At least I'm not the only one to have encountered that error.
On 2009-11-21, at 5:44 AM, çŽ‹æµ© wrote:
> i googled the problem,it says that's a mysql bug.This is the source page :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 the source database and then import again.
> Best wishes!