Re: RFC: ext/mysql deprecation

From: Date: Mon, 19 Nov 2012 13:52:17 +0000
Subject: Re: RFC: ext/mysql deprecation
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20  Groups: php.internals 
Request: Send a blank email to internals+get-63972@lists.php.net to get a copy of this message
On Sat, 2012-11-17 at 16:19 +0100, Ángel González wrote: > What are those benefits that mean everyone needs to move to mysqli? > I was making myself the opposite question :) With ext/mysql you, for instance, can not - use stored procedures (there's no "mysql_next_result" or such) - use SSL with custom keys (or some other "advanced" security/authentication features) - use async queries - use prepared statements - ... As also said it's unlikely we'll add support for new server features to ext/mysql, so the gap will grow over time. Of course not everybody needs those, but starting with ext/mysql means you have a hard time if you ever need those in future. > The only reference was about the cost of maingaining it at the beginning > of this > thread, but now Johannes Schlüter said (16 Nov 2012 08:38:19 +0200) that it > doesn't really need work to maintain it. It needs some work, but not tooo much. Might still bring more benefit if the time was spent on feature development. johannes

« previous php.internals (#63972) next »