Re: mysqldump file/data encoding craziness

[Matthew Lenz]

I worry about it as well because it just started. It doesn't happen with our own dumps only when creating this DR dump.

mysqldump --default-character-set=latin1 --set-charset ...

This was one of the multiple dump parameters I tried without success. I assume that is what you are referring to correct?

Why does it still do a:

/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;

before each table create and then right after the create it does:

/*!40101 SET character_set_client = @saved_cs_client */;

?



Edited 1 time(s). Last edit at 05/29/2012 10:55AM by Matthew Lenz.