With version 4.1.9 the server connection collation seems stuck on utf8mb4-general-ci. Selecting utf8-general-ci does not work.
•Server: localhost via TCP/IP
•Server type: MySQL
•Server version: 5.5.20 - MySQL Community Server (GPL)
•Protocol version: 10
•Server charset: UTF-8 Unicode (utf8)
•Apache/2.4.7 (Win32) PHP/5.3.28
•Database client version: libmysql - mysqlnd 5.0.8-dev - 20102224 - $Id: 731e5b87ba42146a687c29995d2dfd8b4e40b325 $
•PHP extension: mysqli
browsers: IE9, Chrome, Firefox
This has been done intentionally, see
https://github.com/phpmyadmin/phpmyadmin/commit/81869b6b
OK. Thanks for your response Marc. It seems utf8mb4 is a new mysql character set that supports 4-byte supplemental characters that are not supported in utf8. I did a little more research and these links provide more info for anyone with questions:
The utf8mb4 Character Set (4-Byte UTF-8 Unicode Encoding)
Upgrading from Previous to Current Unicode Support
Using utf8mb4 with php and mysql
Was there any discussion about using utf8mb4-unicode-ci over utf8mb4-general-ci? I understand the general versions in the past were considered a bit faster, but I also though that now it was considered moot due to modern processors. Was this the reason or is there another for choosing this version?
Food for discussion:
http://stackoverflow.com/questions/766809/whats-the-difference-between-utf8-general-ci-and-utf8-unicode-ci
Starting with phpMyAdmin 4.3.5, default is utf8mb4-unicode-ci. Thanks to David Rahrer.
https://github.com/phpmyadmin/phpmyadmin/commit/c69cf0b74dcc3f88aab0f9149768e420807d254c