Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48789
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 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=b3JMmiUWasBgsj2/SGy1FEdRZQrra+3DtcGl33Al9U78H/JP51e9Ddb5sc0Est1m7Z
         gyCID0Y/FyM29KCFIL2mYYHYNE376PKjP7RJkraVo2Lp28Rogm2Q1tM2P+JaVMhrnTq6
         h1gYcwxKQrhbc2ek5vxNV0XuADMY3g44CnHto=
MIME-Version: 1.0
In-Reply-To: <AANLkTinFdN6t9r5RfkOz-mwG8NWJRKRS3_hUPHVpELCE@mail.gmail.com>
References: <AANLkTikfLjgSvkhYUFqZyDurvRq_5xVLRvjPmFF4PxDO@mail.gmail.com>
	<AANLkTil7lNinMV5e-4K_MyE17_FC5xrC-Gqz0Orbz-X3@mail.gmail.com>
	<AANLkTinFdN6t9r5RfkOz-mwG8NWJRKRS3_hUPHVpELCE@mail.gmail.com>
Date: Tue, 15 Jun 2010 16:56:29 +0200
Message-ID: <AANLkTilU20Ywd9sM09olwn9ruEo6INDtN-PSpZ3A6Gcs@mail.gmail.com>
To: Ilia Alshanetsky <ilia@prohost.org>
Cc: Adam Harvey <aharvey@php.net>, internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Remove sqlite2 from trunk
From: patrick.allaert@gmail.com (Patrick ALLAERT)

What about doing the same with MySQL extensions ?

Currently there is 3 main ways to access a MySQL server:
ext/mysql
ext/mysqli
PDO_MYSQL

Additionally, mysqlnd has to be considered as a possible library for
each of them.

I have the feeling that there is a benefit at removing ext/mysql with
the same arguments as for sqlite 2.

Patrick

2010/6/15 Ilia Alshanetsky <ilia@prohost.org>:
> Just to clarify, removal does not mean deletion, it would simply become a
> PECL extension people who need it can still use.
>
> On Tue, Jun 15, 2010 at 9:30 AM, Adam Harvey <aharvey@php.net> wrote:
>
>> On 15 June 2010 19:41, Ilia Alshanetsky <ilia@prohost.org> wrote:
>> > After speaking to a few developers in DPC, I think it makes sense for =
us
>> to
>> > drop the Sqlite2 extensions from Trunk as they are superseded by the
>> Sqlite3
>> > extensions. The sqlite2 library is no longer maintainer and the migrat=
ion
>> > path from version 2 to 3 is very simple. Unless there any objections, =
I'd
>> > like to make this happen in the next week or two.
>>
>> Funnily enough, we had a short discussion about this on IRC last week;
>> I was meaning to write an RFC before getting swamped at work. My
>> feeling (and I'm speaking just for myself here) is that we can't
>> really get rid of ext/sqlite in the short to medium term: people have
>> gotten too used to having it available and bundled in a default PHP
>> installation. Obviously, though, we can't really keep bundling an
>> unmaintained library, either, and we should start nudging people
>> gently towards sqlite3.
>>
>> What I'd prefer:
>>
>> =E2=80=93 Deprecate ext/sqlite in trunk, at least by having sqlite_open(=
)
>> generate an E_DEPRECATED warning.
>> =E2=80=93 Unbundle libsqlite2 in the next major version after what's cur=
rently
>> in trunk and disable the extension by default, but still allow
>> compilation against an external libsqlite2 if the user really wants
>> to.
>> =E2=80=93 Move ext/sqlite to PECL at some point thereafter.
>>
>> PDO would be handled similarly.
>>
>> If someone has some real world numbers on the use of ext/sqlite, that
>> might be handy. From where I sit, though, it does seem to have become
>> a bit of a standard, so I'd rather not pull the rug out from under
>> people that suddenly =E2=80=94 particularly given it's not even deprecat=
ed at
>> the moment.
>>
>> Adam