why client characterset and sever characterset are set to Latin when character set client and server are set to different character set
Posted by: Sam Ohn
Date: November 10, 2010 03:54PM

I set up utf-8 character set for server, client, connection, etc.
When I run SHOW command to check the character set setting, Character set for client, connection, database, results, server... are utf8. However, when I run STATUS command, Client characterset and Server characterset are set to Latin1.
I thought Client characterset and Server characterset should be set to utf8. Do you know why they were set to Latin1?
I appreciate any comments, suggestions, etc.

I use Window 7 Home 64 W/ Japanese for non-unicode applications
Mysql version 5.1.41

Thank you in advance

Sam

mysql> show variables like '%char%';
+--------------------------+--------------------------------+
| Variable_name            | Value                          |
+--------------------------+--------------------------------+
| character_set_client     | utf8                           |
| character_set_connection | utf8                           |
| character_set_database   | utf8                           |
| character_set_filesystem | binary                         |
| character_set_results    | utf8                           |
| character_set_server     | utf8                           |
| character_set_system     | utf8                           |
| character_sets_dir       | C:\xampp\mysql\share\charsets\ |
+--------------------------+--------------------------------+

But, when I used STATUS command,

mysql> status
--------------
mysql  Ver 14.14 Distrib 5.1.41, for Win32 (ia32)

Connection id:          27
SSL:                    Not in use
Using delimiter:        ;
Server version:         5.1.41 Source distribution
Protocol version:       10
Connection:             localhost via TCP/IP
Client characterset:    latin1    
Server characterset:    latin1
TCP port:               3306
Uptime:                 2 min 5 sec



Edited 2 time(s). Last edit at 11/10/2010 06:47PM by Sam Ohn.

Options: ReplyQuote




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.