MySqli migration tool, now you have no excuse to migrate!
Posted by Pierre in
PHP
Friday, October 13. 2006
Earlier this week, I was discussing ext/mysql and ext/mysqli with Ilia and a couple of php devs on IRC. It happens that I have a strong opinion about ext/mysql future, it has none 
(it is a mysql-mysql question, PDO is not a solution as we were talking about mysql-only problems and solutions.)
The discussion was about what would be the best thing to do for ext/mysql and Unicode (aka php6), as it is not possible to implement unicode support for this extension. My opinion is that Georg and his team put a lot of effort in mysqli since years. It is production ready since the very first version of PHP 5, MySQL 3.x servers are dead cows. Why should they continue to maintain this extension? Or why should it be available by default in php6? It seems that MySQL’s plan is to keep it in php without unicode support, I think it is a bad idea, but hey, if they like to maintain it until the end of times ;- )
Everyone using mysql only features (new ones or old ones) should update and better sooner than later. And the good news (and timing is that Colin Charles announced the immediate availability of the MySQLi converter tool. They also published a step by step guide to convert Wordpress to mysqli, as an example.
Still here? Go update!
NB: Georg has commited MySQLi unicode support, play with it and report bugs
