Comments on: mySQL forcing utf-8 compliance for all connections.

By: moon

moon — Tue, 15 Jun 2010 14:57:10 +0000

i’ve just slapped myself.
good doc btw. ty.

By: Oliver Nassar

Oliver Nassar — Thu, 07 Jan 2010 10:04:55 +0000

“When a client connects to the server, it sends the name of the character set that it wants to use. The server uses the name to set the character_set_client, character_set_results, and character_set_connection system variables. In effect, the server performs a SET NAMES operation using the character set name.”

–
found that in mysql’s docs. is that saying that since we have the init_connect setting, when we connect to the db, from say a php script, it’ll automatically set those three settings accordingly on it’s own?

By: Oliver Nassar

Oliver Nassar — Thu, 07 Jan 2010 09:08:17 +0000

Quick question. Looking through `show variables;` I see the following, seemingly character/collation related variables:
character_set_client
character_set_connection
character_set_database
character_set_results
character_set_server
character_set_system

collation_connection
collation_database
collation_server

The reason I say related, is because by default they all have a latin based character/collation value on a fresh mysql install. Your command switches all but the following to utf8/utf8_general_ci:
character_set_client
character_set_connection
character_set_results
collation_connection

Those remain latin1/latin1_swedish_ci

—-
My question is, do these not need to be set manually as all databases will now be created accordingly in utf8/general? Is there a reason them being latin based doesn’t cause issues? I would assume making them the appropriate utf8 type would make it more consistent, but am curious what they would affect. I assumed (based on their names alone) that the connection ones (character_set_connection, collation_connection) might be of interest.

Any thoughts?

By: Massimiliano

Massimiliano — Fri, 13 Nov 2009 11:41:23 +0000

Thanks Buzz,
you saves my life! i was stuck since 9.00 AM…

By: Michael’s Tech Blog » Additional mysql server UTF8 confutation

Michael’s Tech Blog » Additional mysql server UTF8 confutation — Fri, 09 Oct 2009 11:51:00 +0000

[...] [via Saiweb] [...]

By: Converting mySQL latin1 to utf8 | Saiweb

Converting mySQL latin1 to utf8 | Saiweb — Tue, 14 Jul 2009 08:47:11 +0000

[...] Force mySQL utf8 connections [...]

By: Olle

Olle — Mon, 22 Jun 2009 12:48:50 +0000

Thank you! Works great

By: MySQL + UTF-8 = Not So Obvious « Ward’s Words

MySQL + UTF-8 = Not So Obvious « Ward’s Words — Sat, 28 Mar 2009 07:56:16 +0000

[...] existing literature on the topic including possible fixes [here, here, here, here, here, here, horror story here, here] encourage the configuration of the MySQL daemon (mysqld) to [...]

By: Nicolai Schlenzig

Nicolai Schlenzig — Fri, 28 Nov 2008 22:28:34 +0000

Thank you!

I have been looking everywhere for hints on how to get UTF-8 working on my new server.

This installation is a fully updated FreeBSD 7.0 with Apache 2.2.9 and MySQL 5.0.67.

When importing my old utf8_general_ci database everything looked fine… but reading it from my website showed characters wrong. Writing new entries into the database (from web) made something unreadable to the human eye for special chars like æøåöëü etc.

I have tried SO many options for both Apache, MySQL and my own (perl) code.

Page bookmarked! (and I will copy some info to my soon to come wiki http://www.confighell.com)

Thanks again

– Nicolai