Re: RFC: ext/mysql deprecation

Rasmus Lerdorf wrote: > On 11/16/2012 01:34 AM, Ryan McCue wrote: >> Pierre Joye wrote: >>> Wordpress lead developer statement is rather clear: Go ahead, we will follow. >> >> Indeed, we have patches written already [1], but they were low priority. >> The plan is to aim for landing these in the next major version, assuming >> PHP does go ahead with this. >> >> [1]: http://core.trac.wordpress.org/ticket/21663 > > So, I am curious, why are you waiting on us for this? Is it because > ext/mysql does everything you need and you simply have no need for any > of the new and obviously better features in mysqli? I would have thought > you would have switched to mysqli years ago if it was available and only > used ext/mysql as a desperation fallback if that was all that was available. I can't speak for all of WordPress' history, but generally, it works well enough. That's one of the reasons addslashes() was used instead of mysql_real_escape_string() for a long time (and can still occur). It's a crucial component, and hence changes to it (especially larger ones) fall under "if it ain't broke, don't fix it". The gains in mysqli/PDO just aren't enough to justify the changes. For example, prepared statements are a large advantage of mysqli/PDO. The problem is, the way database access is done in WordPress means that they couldn't be used in a backwards compatible way (although I think we may be able to fix that). -- Ryan McCue <http://ryanmccue.info/>