Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53885
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain rile.ca from 208.113.200.5 cause and error)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; c=nofws; d=rile.ca; h=reply-to:from:to
	:references:in-reply-to:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=rile.ca; b=Ksv
	dT9noLnxCHzzVZ4LmzngrDiToO/mcQ6ABDiJGGwDqBF9XPbJFK5PPBLGMI11n0WI
	LL+4JC+QVE2lAkPdiWw/23W0MF9Qfwcm7JESuJJBlipx8tjFYAcdrmNLBIFIzJj/
	soYlxCn4gZzcLM42EjyNMMkPU8IiN1wqbFWCXrBw=
Reply-To: <mike@rile.ca>
To: "'Matthew Weier O'Phinney'" <weierophinney@php.net>,
	<internals@lists.php.net>
References: <9F1FA580-FD3F-4C3F-9E26-51A095CF6EE9@roshambo.org> <4E1B19B7.60703@oracle.com> <CAKxcST8ugYMMn690SGLKEQXDib-9+S-HXxJJpXqjDRqikMdAsg@mail.gmail.com> <A2.F2.30857.A593B1E4@pb1.pair.com>
In-Reply-To: <A2.F2.30857.A593B1E4@pb1.pair.com>
Date: Mon, 11 Jul 2011 14:47:25 -0400
Message-ID: <003a01cc3ffa$fbb4dd50$f31e97f0$@ca>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acw/9AoLdyaf0lCQT2q/SeWf0uTxnwAA/8NQ
Content-Language: en-ca
Subject: RE: [PHP-DEV] deprecating ext/mysql
From: mike@rile.ca ("Mike Robinson")

On July-11-11  Matthew Weier O'Phinney wrote:

> Sent: July-11-11 1:57 PM
> To: internals@lists.php.net
> Subject: Re: [PHP-DEV] deprecating ext/mysql
> 
> On 2011-07-11, Paul Dragoonis
> >
> > Yes, +1 from me too. I do indeed think we need to make this a smooth
> > transition over time. Possibly triggering an E_DEPRECATED for all
> > ext/mysql usage. Just like the introduction of E_DEPRECATED for 5.3
> > functions, we could apply the same approach here. After 5.4 is
> > released we can put big "Deprecated Warning" notifications on all
> > php.net/mysql_* functions too. I think we all want this, but to be
> > realistic from a production point of view, many sites will still be
> > using ext/mysql.
> 
> And, to my reading, this is exactly the path that was recommended. The
> point is to start a "soft" deprecation now via the manual, indicating
> that users should migrate to other solutions, while simultaneously
> detailing how to do equivalent operations via ext/mysqli or pdo_mysql.
> Actual deprecation would happen later.

I haven't looked at the mysql_* section of the manual in 15 years. It
would not surprise me to learn that that was one of the least viewed
areas of manual.

I'd be curious to see what kind of response this suggestion would elicit
from the PHP General list.

From the MySQL site:

"We have no plans to remove libmysql support from ext/mysql, ext/mysqli
or PDO_MYSQL, which would break existing applications. We just add a new,
superior alternative to our PHP offerings."

So I'd also be interested to hear what the MySQL folks had to say about
this.

If a laissez-faire approach is taken a lot of people are going to have
bite marks on their behinds.

Mike