It is therefore highly recommended to avoid
switching character sets if our system is not configured to do the necessary conversion.
Importing and Exporting with Character Sets
If $cfg['AllowAnywhereRecoding'] is set to TRUE, then the File to import section of
the Import sub-pages is modified, so that we can choose a character set for the file to
be imported:
Character Sets and Collations
[ 258 ]
In the Export dialog, we can also choose the character set of the file to be created:
MySQL 4.1.x and Later
Since MySQL 4.1.x, the MySQL server does the character recoding work for us.
Also, MySQL enables us to indicate the character set and collation for each database,
each table, and even each field. A default character set for a database applies to each
of its tables, unless it is overridden at the table level. The same principle applies to
every field.
Since phpMyAdmin 2.6.0, support for MySQL 4.1.x character set and collation
features is no longer experimental, as it was in previous versions.
The $cfg['AllowAnywhereRecoding'] parameter has no impact for MySQL
version 4.1.x and later, except to enable the Character set of the file drop-down
menu in the Export sub-page.
Collations
When strings have to be compared and sorted, precise rules must be followed by
the system (MySQL, in this case). For example, is 'A' equivalent to 'a'? Is 'Andr?©'
equivalent to 'Andre'? A set of these rules is called a collation.
Pages:
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238