RE: About character_set_*
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:rja...@yahoo-inc.com] Sent: Wednesday, August 08, 2012 2:55 AM To: Zhigang Zhang; mysql@lists.mysql.com Subject: RE: About character_set_* The answer is long and involved... http://mysql.rjweb.org/doc.php/charcoll -Original Message- From: Zhigang Zhang [mailto:zzgang2...@gmail.com] Sent: Tuesday, August 07, 2012 3:25 AM To: mysql@lists.mysql.com 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. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: About character_set_*
The answer is long and involved... http://mysql.rjweb.org/doc.php/charcoll -Original Message- From: Zhigang Zhang [mailto:zzgang2...@gmail.com] Sent: Tuesday, August 07, 2012 3:25 AM To: mysql@lists.mysql.com 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. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: About character_set_*
Unless your effort is to convert all text strings to Mainland Chinese only ...Dont forget 'Locale' http://dev.mysql.com/doc/refman/5.5/en/locale-support.html Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. From: rja...@yahoo-inc.com To: zzgang2...@gmail.com; mysql@lists.mysql.com Date: Tue, 7 Aug 2012 11:55:15 -0700 Subject: RE: About character_set_* The answer is long and involved... http://mysql.rjweb.org/doc.php/charcoll -Original Message- From: Zhigang Zhang [mailto:zzgang2...@gmail.com] Sent: Tuesday, August 07, 2012 3:25 AM To: mysql@lists.mysql.com 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. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
