Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48999
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:content-transfer-encoding;
        b=KhhjSRjOGjTE9QyArCC1RPOA3UiSuNyxoAKlsH2EmMikv2QdRCzus5xpemgrLu74Gf
         a27kPpFWNcW2nl59c+JaqGzw2GMfnC3DBEsOCma8fDQphVSEYHE4ecs0Ldya2Nmf/9R4
         AE43JtWWS62dxpG0uo7YvebTtlRjf4NUy3lDQ=
MIME-Version: 1.0
In-Reply-To: <4C2E0984.5040607@oracle.com>
References: <AANLkTikudsMYBZVhmkAjrZX5Zw4oSxpdwDLAA-oGXemq@mail.gmail.com>
	<4C2E0984.5040607@oracle.com>
Date: Sat, 3 Jul 2010 11:40:55 -0700
Message-ID: <AANLkTik4JJ-VMgo07Du3cxdrvoBvYlxVbYj-ulYpwsM2@mail.gmail.com>
To: Christopher Jones <christopher.jones@oracle.com>, Ilia Alshanetsky <ilia@prohost.org>, 
	=?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] PDO DBLIB Release Candidate?
From: ssufficool@gmail.com (Stanley Sufficool)

On Fri, Jul 2, 2010 at 8:45 AM, Christopher Jones
<christopher.jones@oracle.com> wrote:
>
>
> On 07/02/2010 07:11 AM, Stanley Sufficool wrote:
>>
>> Can I get an affirmation if the pdo dblib code will be accepted in 5.2
>> and 5.3 branches?
>>
>
> It shouldn't go into 5.2 if it introduces new functionality. =A0You
> might backport the crash/leak bug fixes if Ilia is OK with that.

Patches for the OOM for 5.2 and 5.3 are attached to BUG #50755
http://bugs.php.net/bug.php?id=3D50755

There has been feedback on this bug that indicates other are needing
this fix as well. This prevents people from developing bigger
applications on non-MS Platforms to support SQL Server and Sybase.

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. This passes *most* PDO tests and passes other
tests in ext/pdo_dblib/tests. The PDO tests that fail, AFAIK have
always failed.

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.

BTW, This extension is experimental and subject to change. Well it
did, and they were warned.

Happy Independence Day,
Stan

>
> Depending if how compatible (UI + protocol) it is with 5.3, then
> Johannes may accept it into 5.3.4.
>
> I'm concerned that recent PDO changes (including Ilia's merge of
> inTransaction() for Postgres) haven't been documented. =A0Lack of
> accurate documentation won't help the consistency of further PDO
> driver changes.
>
> Chris
>
> --
> Email: christopher.jones@oracle.com
> Tel: =A0+1 650 506 8630
> Blog: =A0http://blogs.oracle.com/opal/
> Free PHP Book: http://tinyurl.com/ugpomhome
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>