mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 12:32:27 +01:00
bee9933ab8
support-files/mysql.server-sys5.sh: Change mode to -rw-rw-r-- Docs/manual.texi: Added information about BeOS, Access 2000, AIX and user links client/mysql.cc: Fixed SOURCE to work on windows client/mysqldump.c: Strip of white space configure.in: Fix for AIX include/dbug.h: Assert handling include/my_pthread.h: Ia64 needs more thread stack than other processors include/my_sys.h: More comments myisam/mi_key.c: Fixed wrong key length checks mysql.proj: update mysys/charset.c: Cleanup mysys/mf_keycache.c: Moved SEC_LINK to file that used it mysys/my_static.h: Moved SEC_LINK to file that used it scripts/Makefile.am: Fix for debian scripts/mysql_install_db.sh: Cleanup sql/gen_lex_hash.cc: Better values sql/ha_berkeley.cc: Fix of reading of unique key sql/handler.cc: Fix memory allocation bug sql/mysqld.cc: Fix for Ia64 sql/share/charsets/latin1.conf: Fixed sortorder back to scandinavian. sql/sql_yacc.yy: FULL shouldn't be a keyword support-files/Makefile.am: Fix for debian support-files/mysql.server.sh: Cleanups |
||
---|---|---|
.. | ||
cp1251.conf | ||
cp1257.conf | ||
croat.conf | ||
danish.conf | ||
dec8.conf | ||
dos.conf | ||
estonia.conf | ||
german1.conf | ||
greek.conf | ||
hebrew.conf | ||
hp8.conf | ||
hungarian.conf | ||
Index | ||
koi8_ru.conf | ||
koi8_ukr.conf | ||
latin1.conf | ||
latin2.conf | ||
README | ||
swe7.conf | ||
usa7.conf | ||
win1250.conf | ||
win1251ukr.conf |
This directory holds configuration files which allow MySQL to work with different character sets. It contains: *.conf Each conf file contains four tables which describe character types, lower- and upper-case equivalencies and sorting orders for the character values in the set. Index The Index file lists all of the available charset configurations. Each charset is paired with a number. The number is stored IN THE DATABASE TABLE FILES and must not be changed. Always add new character sets to the end of the list, so that the numbers of the other character sets will not be changed. Compiled in or configuration file? When should a character set be compiled in to MySQL's string library (libmystrings), and when should it be placed in a configuration file? If the character set requires the strcoll functions or is a multi-byte character set, it MUST be compiled in to the string library. If it does not require these functions, it should be placed in a configuration file. If the character set uses any one of the strcoll functions, it must define all of them. Likewise, if the set uses one of the multi-byte functions, it must define them all. See the manual for more information on how to add a complex character set to MySQL. Syntax of configuration files The syntax is very simple. Comments start with a '#' character and proceed to the end of the line. Words are separated by arbitrary amounts of whitespace. For the character set configuration files, every word must be a number in hexadecimal format. The ctype array takes up the first 257 words; the to_lower, to_upper and sort_order arrays take up 256 words each after that.