Re: mysqldump file/data encoding craziness
> I believe debian recently moved to using utf-8 as the default file character set.
Are you stating something about the Operating system, or about mysql??
> We also have another app based on the same code and it's dumps always result in a 'file' command of UTF-8.
What 'file' command? The one in the OS? What are you trying to tell us?
> So I instead of grepping out the import tokens.
Elaborate.
> dump/load ALL the table creates
via mysqldump? Please provide the command arguments that you used.
> example of the tokens
What do you mean by "token"?
"-- " introduces a comment that lasts until the end of the line.
> /*!40101 SET NAMES utf8 */;
That says that the rest of the mysqldump file will be _interpreted_ as utf8-encoded.
> /*!40101 SET character_set_client = utf8 */;
This is a part of the SET NAMES; again, it says that the dump is interpreted as utf8.
I highlighted "interpreted" because if the bytes are not in utf8, you have a mess.
Subject
Views
Written By
Posted
4553
May 23, 2012 09:40AM
Re: mysqldump file/data encoding craziness
1929
May 26, 2012 11:09PM
3935
May 27, 2012 01:44PM
2036
May 28, 2012 09:52AM
1950
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.