Character Sets and Collations - Mastering phpMyAdmin 2.8 for Effective MySQL Management - page 248

'phone' varchar(30) collate latin1_general_ci default NULL,
'country_code' char(2) collate latin1_general_ci NOT NULL default '',
PRIMARY KEY ('author_id')
) ENGINE=MyISAM DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci;

Server View
In the Server view, we can obtain statistics about the databases. (See the Database
Information section in Chapter 18.) If our server supports character sets and collations,
we will see an additional information column, Collation , on this page:

Kanji Support
If phpMyAdmin detects usage of the Japanese language, it checks whether PHP
supports the mb_convert_encoding() multi-byte strings function. If it does,
additional radio buttons are displayed on the following pages so that we can choose
between the EUC-JP and SJIS Japanese encodings:

•
•
•

export
insert text from a file
query box

Summary
In this chapter, we covered the use of language files in phpMyAdmin. We looked at
UTF-8 and the impact of switching from one character set to another. We also saw
how phpMyAdmin has to recode data when the version of MySQL is earlier than
4.1.x, and we looked at the character set and collation features of MySQL version
4.1.x and later.