Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48786
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain adamharvey.name from 209.85.212.42 cause and error)
MIME-Version: 1.0
Sender: adam@adamharvey.name
In-Reply-To: <AANLkTikfLjgSvkhYUFqZyDurvRq_5xVLRvjPmFF4PxDO@mail.gmail.com>
References: <AANLkTikfLjgSvkhYUFqZyDurvRq_5xVLRvjPmFF4PxDO@mail.gmail.com>
Date: Tue, 15 Jun 2010 21:30:57 +0800
Message-ID: <AANLkTil7lNinMV5e-4K_MyE17_FC5xrC-Gqz0Orbz-X3@mail.gmail.com>
To: Ilia Alshanetsky <ilia@prohost.org>
Cc: 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: aharvey@php.net (Adam Harvey)

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 Sqli=
te3
> extensions. The sqlite2 library is no longer maintainer and the migration
> 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 curren=
tly
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 deprecated =
at
the moment.

Adam