Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71636
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain hristov.com from 91.196.124.214 cause and error)
Message-ID: <52E64D10.5020404@hristov.com>
Date: Mon, 27 Jan 2014 14:12:00 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CADajX4AzUWh4-DALP_-fkpfPB+CMK4NvNJ2ByzmAUz2wGW8n4w@mail.gmail.com> <52E29253.2000801@lsces.co.uk> <52E2924B.6080002@ajf.me> <CAMUwpuS0KzwJWO=8Pfxdfwe8BuYPcPLHTrcB7ubfafXJ2020FQ@mail.gmail.com> <52E299D4.6040102@garfieldtech.com> <CAMUwpuTe_ACUhznyO6c=t1kJitb=UnfR2jK9yh_HPi=QeQNzug@mail.gmail.com> <52E2C98C.6010005@lerdorf.com> <CAL0xaBHtjNMb8HCc5zMP+xQVJgSVMEtqbBX-4h_gbURTKSKxsg@mail.gmail.com> <52E2D8D2.80106@lerdorf.com>
In-Reply-To: <52E2D8D2.80106@lerdorf.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Ruminations on PHP 5++
From: php@hristov.com (Andrey Hristov)

On 24.01.2014 23:19, Rasmus Lerdorf wrote:
> On 1/24/14, 1:03 PM, Arvids Godjuks wrote:
>> The PDO. This is something that needs so much improvement that it's
>> ridicilous it has survived till this time. I use Yii framework as my tool,
>> they use PDO as their base. I have considered many times to integrate a
>> mysqli to PDO wrapper to bring things like mysqli_ping, unbuffered queries
>> and lost more. At this point I can do without those things because I do not
>> have a lot of load on my projects, but they are growing and at some point
>> abandoning the PDO will be a nesesity due to it's lack of features.
>> I think PDO is a bad idea for PHP as a whole. We are better of with a
>> consisten API through the native drivers and maybe a PDO like thing that
>> gives us data objects, but still provides ability to get to the low level
>> stuff that is sometimes needed. PHP lately has moved to projects that
>> previosly where done on Java and some other move advanced tech. And lack of
>> frameworks using the native drivers is kind'a bad, because in really
>> advanced projects you have to create your own framewok...
>
> But note, if you blindly switch from PDO to mysqli, which in turn
> usually means moving from client-side prepares to server-side prepares,
> chances are you are going to take a significant performance hit. Like I
> said, it means two extra network roundtrips per sql query and for one
> large project I worked on that meant an extra 40ms latency per web request.

in the case most of the queries happen to be prepared over and over 
again there is some solution to this :
http://svn.php.net/viewvc/pecl/mysqlnd_pscache/trunk/

It plays with persistent connections, doesn't close them and when a PS 
is tried to be prepared and is on the same connection there is no 
round-trip and the PS is reused. Of course, all problems of pconns stay. 
It's more of a PoC but in simple tests it worked.

> So I don't think PDO is a bad idea. Having a single source of common
> functionality needed by all DB drivers makes sense. Imagine if every
> lower-level driver needed to implement their own client-side prepare
> feature? And a consistent API across the low-level drivers isn't
> feasible since each DB has a lot of specialization. It would end up
> looking exactly like PDO but with a bunch of special calls for each one.
> If you could bounce back and forth between PDO and the lower-level
> driver easily you get the consistent API and you get access to all the
> lower-level features. Also, from a migration point of view, scrapping
> PDO and rewriting all the low-level drivers to be "consistent" would be
> an absolute nightmare.
>
> -Rasmus
>

Best,
Andrey