From: Zhigang Zhang
Date: August 8 2012 11:04am
Subject: RE: About character_set_*
List-Archive: http://lists.mysql.com/mysql/227966
Message-Id: <502247de.6a88440a.21b4.6600@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit


I know this, But I think the variable "character_set_connection" is
unnecessary.

Because the server know the table's encoding, So it can convert the encoding
from "character_set_client" to the table's encoding.

-----Original Message-----
From: Rick James [mailto:rjames@stripped] 
Sent: Wednesday, August 08, 2012 2:55 AM
To: Zhigang Zhang; mysql@stripped
Subject: RE: About character_set_*

The answer is long and involved...
  http://mysql.rjweb.org/doc.php/charcoll

> -----Original Message-----
> From: Zhigang Zhang [mailto:zzgang2008@stripped]
> Sent: Tuesday, August 07, 2012 3:25 AM
> To: mysql@stripped
> Subject: About character_set_*
> 
> Hello.
> 
> 
> 
> As I know, when client send data to server, the encoding converting
> process
> is:
> 
> 
> 
> character_set_client  -->  character_set_connection --> db table
> encoding.
> 
> 
> 
> I think it is a short path than above way:
> 
> 
> 
> character_set_client  -->  db table encoding.
> 
> 
> 
> Why it is converted to "character_set_connection"?
> 
> 
> 
> 
> 
> Yours
> 
> Zhigang.