Re: mysqldump file/data encoding craziness
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.
Subject
Views
Written By
Posted
4553
May 23, 2012 09:40AM
1929
May 26, 2012 11:09PM
3935
May 27, 2012 01:44PM
2036
May 28, 2012 09:52AM
Re: mysqldump file/data encoding craziness
1949
May 29, 2012 10:50AM
1655
May 30, 2012 07:51PM
1583
May 31, 2012 07:27AM
1749
June 12, 2012 10:47PM
1494
July 03, 2012 02:46PM
1709
July 04, 2012 04:37PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.