Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
MariaDB
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
MariaDB
Commits
54190bc0
Commit
54190bc0
authored
May 28, 2008
by
Georgi Kodinov
Browse files
Options
Browse Files
Download
Plain Diff
automatically merged
parents
ed786398
c9232b93
Changes
2
Expand all
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
113 additions
and
68 deletions
+113
-68
sql/share/charsets/README
sql/share/charsets/README
+19
-20
strings/CHARSET_INFO.txt
strings/CHARSET_INFO.txt
+94
-48
No files found.
sql/share/charsets/README
View file @
54190bc0
This directory holds configuration files
which allow
MySQL to work with
This directory holds configuration files
that enable
MySQL to work with
different character sets. It contains:
*.conf
Each conf file contains four tables which describe character types,
charset_name.xml
Each charset_name.xml file contains information for a simple character
set. The information in the file describes 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.
Index.xml
The Index.xml file lists all of the available charset configurations,
including collations.
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.
Each collation must have a unique number. The number is stored
IN THE DATABASE TABLE FILES and must not be changed.
The max-id attribute of the <charsets> element must be set to
the largest collation number.
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 c
onfiguration
file?
(libmystrings), and when should it be placed in a c
harset_name.xml
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.
placed in a c
harset_name.xml c
onfiguration 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
...
...
@@ -30,11 +33,7 @@ Compiled in or configuration file?
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.
The syntax is very simple. Words in <map> array elements are
separated by arbitrary amounts of whitespace. Each word must be a
number in hexadecimal format. The ctype array has 257 words; the
other arrays (lower, upper, etc.) take up 256 words each after that.
strings/CHARSET_INFO.txt
View file @
54190bc0
This diff is collapsed.
Click to expand it.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment