LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - General (http://www.linuxquestions.org/questions/linux-general-1/)
-   -   mono / odbc / mysql charset issues. (http://www.linuxquestions.org/questions/linux-general-1/mono-odbc-mysql-charset-issues-4175426197/)

Robster400 09-07-2012 11:52 PM

mono / odbc / mysql charset issues.
 
Ok, I've got a gameserver controller (procon) running on mono on Debian squeeze.
It has a player stats & chat logger, via a plugin, which sends data to a mysql db.

I've moved it from a Windows machine, where its been working great for months, and apart from the logging problems, seems to be fine on top of mono.

So, what is happening? Instead of filling the db with playernames & chat log entries, its filling it with invalid chars. It should be noted that all text to be logged is English with no unusual characters.

When the plugin & sql db were all at default Latin1, it filled the db with just questionmarks, so I changed all references of Latin1 to utf8 in the procon plugin source (its compiled on the fly at launch), and set MySQL to utf8, and now it fills the db with Asian/Chinese characters....

I guess somewhere the correct encoding is not being translated somehow, but its a little above my head.
Any ideas anyone?

/etc/odbc.ini
Code:

[ODBC Data Sources]
procon  = MySQL ODBC 5.1 Driver
#
#
[procon]
Description = Procon connection
Driver = /usr/lib/odbc/libmyodbc5.so
SERVER = Localhost
DATABASE = myDBname
PORT = 3306
UID = DBuser
PWD = DBpassword
Socket = /var/run/mysqld/mysqld.sock
Option = 3
Stmt =

/etc/odbcinst.ini
Code:

[MySQL ODBC 5.1 Driver]
Description = Procon connection
Driver = /usr/lib/odbc/libmyodbc.so
Setup = /usr/lib/odbc/libodbcmyS.so
CPTimeout =
CPReuse =
FileUsage = 1


[ODBC Drivers]
MySQL ODBC 5.1 Driver = Installed

my.conf
Code:

#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port                      = 3306
socket                      = /var/run/mysqld/mysqld.sock
default-character-set=utf8

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket                = /var/run/mysqld/mysqld.sock
nice                = 0

[mysqld]
#
# * Basic Settings
#
user                = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket                = /var/run/mysqld/mysqld.sock
port                = 3306
basedir                = /usr
datadir                = /var/lib/mysql
tmpdir                = /tmp
language        = /usr/share/mysql/english
skip-external-locking
#
# Charset
default-character-set=utf8   
collation-server=utf8_general_ci
init-connect='SET NAMES utf8'
character-set-server=utf8
skip-character-set-client-handshake
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
#bind-address                = 127.0.0.1
# * Fine Tuning
#
key_buffer                = 16M
max_allowed_packet        = 16M
thread_stack                = 192K
thread_cache_size      = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover        = BACKUP
#max_connections        = 100
#table_cache            = 64
#thread_concurrency    = 10
#
# * Query Cache Configuration
#
query_cache_limit        = 1M
query_cache_size        = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file        = /var/log/mysql/mysql.log
#general_log            = 1
#
# Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# Here you can see queries with especially long duration
#log_slow_queries        = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#      other settings you may need to change.
#server-id                = 1
#log_bin                        = /var/log/mysql/mysql-bin.log
expire_logs_days        = 10
max_binlog_size        = 100M
#binlog_do_db                = include_database_name
#binlog_ignore_db        = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet        = 16M

[mysql]
default-character-set=utf8
#no-auto-rehash        # faster start of mysql but no tab completition

[isamchk]
key_buffer                = 16M

#
# * IMPORTANT: Additional settings that can override those from this file!
#  The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/



All times are GMT -5. The time now is 08:23 AM.