Hello. If you switch to the debug binary of the mysqldump, you will be able to find the query which causes 1064 error. See: http://dev.mysql.com/doc/refman/5.0/en/debugging-client.html
Rhino wrote: > Just as a followup to my own remarks, I've tried running my backup > script with the new syntax that Gerald suggested. I was going to wait > for the normal daily backup but I was eager to see if the new version > would work better so I just ran it from the command line. > > Unfortunately, it came back with the same error. The new syntax is still > cleaner and I'm going to keep it but I'm back to square one in > determining why the mysqldump of this one database is giving me trouble. > > Does anyone have any ideas? > > Rhino > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
