Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38928
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain phpdoc.de from 212.227.126.183 cause and error)
Message-ID: <487B1C8E.2010703@phpdoc.de>
Date: Mon, 14 Jul 2008 11:29:50 +0200
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Lars Strojny <lars@strojny.net>
CC: Lukas Kahwe Smith <mls@pooteeweet.org>, 
 PHP Developers Mailing List <internals@lists.php.net>,
 =?ISO-8859-15?Q?Johannes_Schl=FCter?= <johannes@php.net>
References: <C194EFC8-52F2-482E-BD3E-E3D16D33E86C@pooteeweet.org> <1215966417.4685.14.camel@localhost>
In-Reply-To: <1215966417.4685.14.camel@localhost>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] tentative 5.3 release plan
From: ulf.wendel@phpdoc.de (Ulf Wendel)

Lars Strojny schrieb:
> Hi Lukas, hi Johannes,
> 
> Am Freitag, den 11.07.2008, 11:59 +0200 schrieb Lukas Kahwe Smith:
>> - MySQLnd
> 
> what's with PDO MySQLnd, will it be part of 5.3?

The PDO_MYSQLND extension, as I call it, is a patched PDO_MYSQL 
extension. PDO_MYSQLND is on the TODO list [1].

I hardly ever blogged about PDO_MYSQLND as a patch, although it is more 
of a patch than a new extension. PDO_MYSQLND reads shorter than a 
lengthy rather technical explanation.

However, at some point we "forked" PDO_MYSQL and started to patch it to 
optionally support mysqlnd. This was the easiest way to add mysqlnd 
support to the PDO MySQL driver (PDO_MYSQL). PDO_MYSQL was the last 
MySQL extension in row to be upgraded to support both mysqlnd and the 
MySQL Client library (AKA libmysql). ext/mysql and ext/mysqli can 
already be compiled against the MySQL Client library, like ever since (= 
100% BC), or be compiled against mysqlnd.

Early versions of the patch did have a very poor quality. By "poor" I 
mean "poor" - like 60% of the tests crashing. Things became better in 
April (MySQL UC, alpha release). But the April version was still not 
good enough to be checked into the PHP 5.3 CVS repository. It was clear 
that it would take several more months to get the job done with the 
resources assigned to it.

 From the mysqlnd development we know that only very few PHP users are 
interested in bloody steaks. So, why should bad boy MySQL break the 
php.net PHP 5.3 repository and mess up PDO_MYSQL for months instead of 
stabilizing the patch first? In particular if there is no pressing 
reason... Those who want alpha code can get it from us at any time.

We did a tough development sprint in the last weeks to make the patch 
"ready" for the tentative PHP 5.3 release plan. Our internal release 
plan shows no coding between Beta and GA but fixing newly reported bugs. 
All coding was planned to be done by the release of a beta - we have 
reached some 80% of the beta goals.

I expect Dmitry to bail out about PDO_MYSQLND quality and performance. 
Dmitry/Zend is doing some excellent QA behind the scenes. But I do not 
expect any user to complain about us delaying a PHP 5.3 release by 
checking in unstable and buggy code. The patch (PDO_MYSQLND) won't break 
PDO_MYSQL anymore if it goes into the PHP CVS.

Johannes is working on a 3-stars change (***zval) to both PDO and 
PDO_MYSQLND which I would like to test first before the patch 
(PDO_MYSQLND) goes into the PHP 5.3 CVS. That's days, not weeks, just 
enough time to see people discuss the tentative PHP 5.3 release plan and 
the PDO_MYSQLND entry on it.

Ulf

[1] http://wiki.php.net/todo/php53