Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54020
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 as permitted sender)
MIME-Version: 1.0
Sender: doctorrock83@gmail.com
In-Reply-To: <4058F0C7-167E-4600-BBCA-0541E1080EB4@roshambo.org>
References: <9F1FA580-FD3F-4C3F-9E26-51A095CF6EE9@roshambo.org>
 <1310733992.2800.57.camel@guybrush> <4E2038EE.7060600@thelounge.net>
 <1310735398.2800.59.camel@guybrush> <4058F0C7-167E-4600-BBCA-0541E1080EB4@roshambo.org>
Date: Mon, 18 Jul 2011 10:02:12 +0200
Message-ID: <CALEZZWGbNsfvs3wtU6=fZ3MwDoidAVoseHx-OfKOFg5Qe6xA=g@mail.gmail.com>
To: Philip Olson <philip@roshambo.org>
Cc: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes.schlueter@oracle.com>, 
	Reindl Harald <h.reindl@thelounge.net>, internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] deprecating ext/mysql
From: jpauli@php.net (Julien Pauli)

I agree with Johannes and Oracle/MySQL people : ext/mysqli must be the
preferred way to replace ext/mysql.
PDO lacks advanced features which wont be available because of PDO
internals incompatibility.

ext/mysqli is a true MySQL internal API exposure into PHP user land, PDO is=
 not.

Moreover, ext/mysqli has a userland API that is really the same as
ext/mysql one; it's been a design rule of ext/mysqli to ease a future
migration.
PDO is really different and needs objects, not every single PHP
developper is ready to use object nowadays.

Julien.P



2011/7/16 Philip Olson <philip@roshambo.org>:
> Hola friends,
>
> Nice feedback so far, and the PHP documentation will begin implementing
> the ideas presented here, and focus on mysqli but also recommend pdo_mysq=
l.
> Therefore, the ext/mysql documentation will be improved to strongly
> recommend the preferred alternatives that have existed since PHP 5.0.0.
>
> We'll work on the finer details but it feels like procedural mysqli is a
> better fit to live alongside the ext/mysql examples, although we don't wa=
nt
> to confuse people. Maybe geeks here have ideas regarding this, but a clea=
r
> useful clutter-free solution will be worked out, which may include adjust=
ing
> the CSS and involve creative linking. I'll add an example or three soonis=
h.
>
> However, there has been some confusion within the PHP community, so to he=
lp
> ease these concerns:
>
> =A0- This proposal only deals with documentation/education... so it can b=
e
> =A0 described as an official 'soft deprecation' (no errors or code change=
s)
> =A0- When (if?) this extension emits errors, or is removed, is not part o=
f
> =A0 this proposal
> =A0- There is a 100% chance that additional tasks and ideas will be discu=
ssed
> =A0 in the future, which might include:
> =A0 - A conversion tool/guide
> =A0 - A wrapper
> =A0 - A PECL extension
> =A0 - Talking to distros/hosters and apps like wordpress
> =A0 - ...
> =A0- php.net understands that ext/mysql is popular, and we're handling th=
is
> =A0 with extra care and heck, parts of *.php.net is powered by ext/mysql
> =A0- Seriously, no need to panic
>
> We'll document the reasons why the other MySQL extensions are preferred, =
but
> if people want to use the old ext/mysql API with PHP 9.0.0 (just an examp=
le)
> then I'm guessing an old geek out there will make that possible. We, howe=
ver,
> will do our best to convince users to move towards the preferred and
> supported methods, and hopefully write better code along the way because
> honestly, that's the ultimate goal here.
>
> Regards,
> Philip
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>