Snoyes: that’s a.

Bachinski: Jww: the ch****t being used to store the data must match the connection ch****t and client ch****t

Deglandon: Bachinski: I miss the default-character-set directive on the destination server.

Terrall: It’s set to utf8 for mysqldump and mysqlserver on the source server.

Bachinski: Jww: any reference to connection ch****t or client ch****t that isn’t matched?

Lacatena: No I can’t find anything like that.

Stezzi: I found that a character é was replaced by ‘%C3%A9’ , but not all é

Bachinski: Jww: show variables like ‘character_set_%’; — look for default connection ch****t

Dicola: Those characters set are differents !

Budden: On the origin it’s all utf8 , but on the new it’s latin1 for character_set_database and character_set_server

Bachinski: Jww: those defaults are used if there is no ch****t defined at lower levels. no column definition, uses the table definition, no table definition, use the database definition, etc upwards

Nobbe: I see. so it’s not my problem.

Vollenweider: I mean it’s not related.

Bachinski: Jww: well, using the mysql cli client to import utf8 across a connection ch****t of latin1 can be a problem

Bachinski: Jww: does the dumpfile include a statement to SET NAMES utf8? that will set the client and connection to utf8

Bachinski: Jww: of course we’re ***uming the data coming out of the source was correctly stored in the first place :-

Labay: Bachinski: no there is no SET NAMES in my current dump, trough I’ve seen it while doing tests.

Stidman: For each table I see : /*!40101 SET character_set_client = utf8 */;

Murri: I have a very weird suspicion that MySQL avg is giving me wrong result. Could it be possible?

Marohl: Here’s my query & data:

Bachinski: Jww: be nice to use a my.cnf config setting to require utf8 connection setting and do the import over

Mccalop: My.cnf settings are no substitute for SET NAMES

Klier: Hi, can i ask here about MySQL API?

Rolseth: I have a list of values, i want to insert the ones that does not already exist in the table.

Jamel: Is there any elegant way to do that?

Moretz: Insert them all into a temporary table, and then use:


Vanderwood: Alternatively, put a unique constraint on the table, and use INSERT IGNORE.

Narayanan: Snoyes: You mean INSERT INTO . SELECT a.* FROM a LEFT JOIN b ON = WHERE IS NULL;

Brennen: Bachinski: ok I got /*!40101 SET NAMES utf8 */; in the dump file now, I try to restore it.

Milionis: Halvors: yes, something along those lines

Zutell: I’m struggling wit the version text at the end.

Cornely: Mango_: why not use mysql -v?

Leas: Bachinski: nah there is still the same problem :

Leilich: Snoyes: I need to log into the server.

Ralon: Typically you’d put the query part inside quotes

Ottenwess: Mysql -e “show variables like ‘version'”

Somers: I imagine you need the same, maybe with some escaping

Balmaceda: Yes I did try, let me check again.

Schwertfeger: Does Nelles allow off-topic conversation?

Bachinski: Jww: well, are you exporting corrupted data?

Cumpston: Snoyes: double quotes didn’t work, escaping is needed I think

Gheza: Mysql -e “show variables. perhaps

Orta: Bachinski: I see no others options

Gidwani: Relipse: I think you just did

Sevigny: Bachinski: I suspect this since I found the %3C%A9 , it’s some mysql collate stuff I googled about it

Butte: Snoyes: that’s a Niedzwiedzki error.