Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:63953
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.182 as permitted sender)
Message-ID: <50A7C5FB.6070108@gmail.com>
Date: Sat, 17 Nov 2012 18:14:35 +0100
User-Agent: Thunderbird
MIME-Version: 1.0
To: Rasmus Lerdorf <rasmus@lerdorf.com>
CC: PHP Developers Mailing List <internals@lists.php.net>
References: <CADajX4CYZdNpgQv46m_6J7tQLBc=h6HxCn-bGpxr3Ou2VaqgBg@mail.gmail.com> <50A30144.5070305@phpgangsta.de> <50A3BEC0.8030607@gmail.com> <CAET_qdMmhRyidM6_VOokBu6tYvgrPHMOPdzz0PaFpxc3NaTdYQ@mail.gmail.com> <CADajX4Bh+5YrCPEFLzC2qqeJ4NnADbBV0u+wByz3Kb7Jp45KOw@mail.gmail.com> <50A54713.8090102@sugarcrm.com> <CAArmra2bjj3y2UUV8nszU74tN9o4VvB67aXzq5Z1cE2Y_tVijg@mail.gmail.com> <50A549EB.2020408@lerdorf.com> <CAArmra2BCmbOjkK0D8gKc5o0Pwhx0jNGi-3m2C2Z2dAnb0yv7w@mail.gmail.com> <CAAyV7nGMi20xjBYbouvsyUrxdOSuboP6u-guY9DX8qkSagQbjg@mail.gmail.com> <CAEZPtU6mbLnaqijx3T942pULm-Y6a-4LPyk-H-WJ94NckkKbfw@mail.gmail.com> <50A5FB0C.1080602@lerdorf.com> <CACwt+Jdo6WO+VtYp6zSVM+a1GVGQHPxtPT4AAFz2=fQRuxvTWQ@mail.gmail.com> <50A5FF83.1060706@lerdorf.com> <B6638662-0DFB-4679-AEFD-BA8A51DDCD1F@roshambo.org> <CAEZPtU5qFF3hCbN_OF75jViBz=d4kYD=PMpO4J+knqxdiLZB9w@mail.gmail.com> <50A6088B.5010701@rotorised.com> <50A663EF.3020401@lerdorf.com> <50A7AB04.1080805@gmail.com> <50A7BA27.5040701@lerdorf.com>
In-Reply-To: <50A7BA27.5040701@lerdorf.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation
From: keisial@gmail.com (=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=)

On 17/11/12 17:24, Rasmus Lerdorf wrote:
> Right, that is what I meant by focusing more on the carrot than the
> stick. Many people, yourself included, don't realize the things they
> would gain switching to mysqli. We need to do a better job with that and
> perhaps even consider if there are other things we can do in the
> extension to make it more attractive.
Indeed. And it is something to do very carefully. Otherwise, it just looks
like a "we vs them".


> There is a good summary page here:
>
> http://php.net/manual/en/mysqlinfo.api.choosing.php
>
> As you can see there is more to it than just prepared statements.
> Asynchronous queries, for example, is an extremely interesting feature.
It's interesting, but in most cases you will want the results
inmediatly. You
can only take advantage of that if you know in advance your query, and you
are doing anything else in the meantime. It has its uses, but that's not a
complete killer (and makes code harder to follow).
Also, it seems poorly documented, there is mysqli_reap_async_query listed
in php.net but not how to make one :(
A web search discovers a 2008 talk by Ulf, also points to
http://blog.ulf-wendel.de/?p=201 (a 404) but no explanation "this is how
you do it".
A very hacky approach using curl appears much higher :(
http://gonzalo123.com/2010/10/11/speed-up-php-scripts-with-asynchronous-database-queries/

> Being able to fire off your SQL query at the top of a page and then
> instead of waiting around for the result continue building the page
> until you get to the point where you need the DB result.
Do you really expend that much time building your html that it makes a
difference?


> And chances are
> that you will also eventually paint yourself into a corner with
> ext/mysql if you ever need transactions or some of the newer features in
> versions of MySQL beyond 5.1.
BEGIN and COMMIT work quite well :)
I don't know what mysql 5.1+ changes need client support.
Maybe the new ways of password hashing.