mysql client utility character set
My my.ini file is (using MariaDB 5.3.10 in Windows 32-bit):
[mysql] default-character-set=utf8 [client] port=3306 default-character-set=utf8 [client-server] default-character-set=utf8 [client-mariadb] default-character-set=utf8 [mysqld] datadir=C:/webserver/MariaDB/data port=3306 sql_mode="STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION" default_storage_engine=innodb character-set-server=utf8 innodb_additional_mem_pool_size=12M innodb_buffer_pool_size=192M innodb_data_file_path=ibdata1:30M:autoextend:max:300M innodb_flush_log_at_trx_commit=2 innodb_file_format=barracuda innodb_strict_mode=1 innodb_file_per_table=1 innodb_log_file_size=64M key_buffer_size=32M max_allowed_packet = 16M max_connections=60 query_cache_size=16M read_buffer_size=1M read_rnd_buffer_size=2M skip-federated skip-archive sort_buffer_size=1M thread_cache_size=20 tmp_table_size=64M max_heap_table_size=64M table_open_cache=2048 open_files_limit=4096 feedback=ON log_slow_queries=ON
When I connect to the MariaDB server from command line (Windows - cmd.exe) and I type the status command (\s
) I get this:
Server characterset: utf8 Db characterset: utf8 Client characterset: latin1 Conn. characterset: latin1
Why are my default-character-set=utf8
directives in the ini file ignored by the mysql client utility? Is there something I'm missing?
Thanks in advance,
Vasilis
Answer Answered by Vasilis Lourdas in this comment.
Well, after creating the bug, Elena responded in a timely manner. The file would not be read my the mysql client utility at all. I had to copy my.ini to somewhere where the utility would look for it and now it works.
With mysql --help, you get a list of directories where the utility looks for any my.ini or my.cnf file.
Comments
Comments loading...
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.