Latin1 im SQL Server einstellen statt utf8

kekskruemel

Angesehenes Mitglied
Hallo,

ich muss bei meinem Server Debian unter /etc/mysql/my.cnf

die Datenbankverbindung und den Charset auf latin1 umstellen.

Dies habe ich schonn gemacht, so wie ich es u.a. auf anderen Internetseiten gefunden habe.

aber es hilft nichts (auch nach neustart und neuanlegen der Datenbank)

CODE #
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "/var/lib/mysql/my.cnf" to set server-specific options or
# - "~/.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.

[php-apache2handler]

character_set = latin1
character-sets-dir = latin1
default-character-set = latin1

[php-cgi-fcgi]
character_set = latin1
character-sets-dir = latin1
default-character-set = latin1


[php-cli]
character_set = latin1
character-sets-dir = latin1
default-character-set = latin1


[client]
character-sets-dir = /usr/share/mysql/charsets
default-character-set = latin1
character-sets-dir = latin1
character_set = latin1
port = 3306
socket = /var/run/mysqld/mysqld.sock


[mysqladmin]
character-sets-dir = /usr/share/mysql/charsets
default-character-set = latin1
character-sets-dir = latin1

[mysqlcheck]
character-sets-dir = /usr/share/mysql/charsets
default-character-set = latin1
character-sets-dir = latin1


[mysqlimport]
character-sets-dir = /usr/share/mysql/charsets
default-character-set = latin1
character-sets-dir = latin1

[mysqlshow]
character-sets-dir = latin1
default-character-set = latin1

[myisampack]
character-sets-dir = latin1

# 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

skip-bdb

set-variable = innodb_buffer_pool_size=2M
set-variable = innodb_additional_mem_pool_size=500K
set-variable = innodb_log_buffer_size=500K
set-variable = innodb_thread_concurrency=2


[mysqld]
set-variable=local-infile=0
character-sets-dir = /usr/share/mysql/charsets
character-set-server = latin1
default-character-set = latin1
#
# * 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
#
# For compatibility to other Debian packages that still use
# libmysqlclient10 and libmysqlclient12.
old_passwords = 1
#
# 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 = 128K
#
# * Query Cache Configuration
#
query_cache_limit = 1048576
query_cache_size = 16777216
query_cache_type = 1
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log = /var/log/mysql.log
#log = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement :)
#
# Here you can see queries with especially long duration
#log-slow-queries = /var/log/mysql/mysql-slow.log
#
# The following can be used as easy to replay backup logs or for replication.
#server-id = 1
log-bin = /var/log/mysql/mysql-bin.log
# See /etc/mysql/debian-log-rotate.conf for the number of files kept.
max_binlog_size = 104857600
#binlog-do-db = include_database_name
#binlog-ignore-db = include_database_name
#
# * BerkeleyDB
#
# According to an MySQL employee the use of BerkeleyDB is now discouraged
# and support for it will probably cease in the next versions.
skip-bdb
#
# * 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/
#
# If you want to enable SSL support (recommended) read the manual or my
# HOWTO in /usr/share/doc/mysql-server/SSL-MINI-HOWTO.txt.gz
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



set-variable = innodb_buffer_pool_size=2M
set-variable = innodb_additional_mem_pool_size=500K
set-variable = innodb_log_buffer_size=500K
set-variable = innodb_thread_concurrency=2
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
character-sets-dir = latin1
default-character-set = latin1

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


[isamchk]
key_buffer = 16M
character-sets-dir = latin1

 
mySql verwende ich ja nicht.

Aber die obigen Parameter sehen mir allesamt nur nach Verbindungsparametern aus.

Beim Microsoft Sql-Server legt man das entweder auf der Serverebene oder pro Datenbank beim Erstellen fest. Allerdings gibt es da nicht die Optionen ISO/UTF-8/UTF-16, weil die unsinnig sind, sondern nur die Standardsortierung Collation: ISO-8859-1, Binär oder ähnliches.

Welche Daten einzelne Spalten enthalten, wird bei der Definition durch varchar/nvarchar bzw. text/ntext festgelegt. UTF-8 gibt es auf dieser Ebene gar nicht als Option.

Mir scheint, daß mySql UTF-8-Datenströme in varchar-Felder ablegt - und sich dann die Nutzer über tausend Probleme ärgern dürfen.
 
Zurück
Oben