Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49001
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=ojMxbNAU/vkmK8R0OaoTeIgfa3kIqdHQHbsEfHU6eL0dE2MJxfUT+1bszsskb5UHKm
         9fcI1jkYLVbjZQbXI6OPNsHQPXttfZ+Gi9aFcao3NSujmRQJVk9FrTlVmidL/IBnLY21
         oYSaebJbEwdHTgiEmjMbR9ra3yvvkJShMzxn8=
MIME-Version: 1.0
In-Reply-To: <AANLkTinXUi22ICn98X5WqL6eN5HmJuSNvxPy5wtPotQP@mail.gmail.com>
References: <AANLkTikudsMYBZVhmkAjrZX5Zw4oSxpdwDLAA-oGXemq@mail.gmail.com>
	<4C2E0984.5040607@oracle.com>
	<AANLkTik4JJ-VMgo07Du3cxdrvoBvYlxVbYj-ulYpwsM2@mail.gmail.com>
	<AANLkTinXUi22ICn98X5WqL6eN5HmJuSNvxPy5wtPotQP@mail.gmail.com>
Date: Sat, 3 Jul 2010 19:47:43 -0700
Message-ID: <AANLkTilWarIt-TRqsekalBhOrwPFseUU8QaYwkDwmh3w@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: Christopher Jones <christopher.jones@oracle.com>, Ilia Alshanetsky <ilia@prohost.org>, 
	=?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>, 
	internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] PDO DBLIB Release Candidate?
From: ssufficool@gmail.com (Stanley Sufficool)

On Sat, Jul 3, 2010 at 1:07 PM, Pierre Joye <pierre.php@gmail.com> wrote:
> hi,
>
> On Sat, Jul 3, 2010 at 8:40 PM, Stanley Sufficool <ssufficool@gmail.com> wrote:
>
>> I would argue that the additional fixes in trunk fix bugs rather than
>> introducing new functionality since they were already in the PDO
>> specification and they do not break BC. I do not see why this would be
>> held out of releases.
>
> They should, only not right now in 5.3.3/5.2.14 as we are in the
> second release candidates. The reasons why we should not begin to
> apply dozen of patches at this stage are rather obvious, hopefully :).
>

Got it. Thanks.

>
>> FWIW, Microsoft has a monopoly on a fully functional PDO mssql driver
>> which is only implemented on MS platforms. If we want portability of
>> PHP applications, then the PDO DBLIB driver must be fully functional
>> on releases.
>
> That's not correct. PHP 5.3+ has no SqlServer support on Windows. The
> SqlSrv driver is more than welcome as it solves this problem. The PDO
> support is still beta (CTP2). However all other platforms do have
> SqlServer support by default in the core.

Sorry, I was incorrect, the Microsoft PDO SqlServer is still in
release candidate stages. I'm just hoping to have an on-par PDO
implementation available on all platforms before everyone starts
coding for the platform dependent driver.

>
>> BTW, This extension is experimental and subject to change. Well it
>> did, and they were warned.
>
> Hence the worries? :)

I am saying that this extension on the PHP doc pages is marked as
experimental and as such the users should not expect the behavior to
stay consistent. But none-the-less, the patches do not affect any
_existing_ behavior. So no worries. :)

>
> --
> Pierre
>
> @pierrejoye | http://blog.thepimp.net | http://www.libgd.org
>