Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53807
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=C/y
	yEbkaIrND2G/BtjbaHk9+LJDlGQvY/Z2Wv/IR+7EjR8HOGgxUUSIIXtj8v5FMNmn
	gT4G4ZbwalWSXEJiwiHygNvnqIluP3j2H8p0ZyYv1VJyQ+wAi1xXy7p9XEuPe3af
	xFGad1e2iuCG3/90lOzj+mMQ3TEptya6HLJ+ecCg=
Reply-To: <mike@rile.ca>
To: "'Reindl Harald'" <h.reindl@thelounge.net>,
	<internals@lists.php.net>
References: <9F1FA580-FD3F-4C3F-9E26-51A095CF6EE9@roshambo.org> <4E19DE3A.2050303@thelounge.net>
In-Reply-To: <4E19DE3A.2050303@thelounge.net>
Date: Sun, 10 Jul 2011 16:20:46 -0400
Message-ID: <000301cc3f3e$db4339c0$91c9ad40$@ca>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acw/JSoghsQMyfZTSESTt3OKYBqvmgAF+dPg
Content-Language: en-ca
Subject: RE: [PHP-DEV] deprecating ext/mysql
From: mike@rile.ca ("Mike Robinson")

On July-10-11 1:16 PM Reindl Harald wrote:
> Am 10.07.2011 19:03, schrieb Philip Olson:
> > What this means to ext/mysql:
> >
> > - Softly deprecate ext/mysql with education (docs) starting today
> > - Not adding E_DEPRECATED errors in 5.4, but revisit for 5.5/6.0
> > - Add pdo_mysql examples within the ext/mysql docs that mimic the
> > - current examples, but occasionally introduce features like
> > -  prepared statements
> > - Focus energy on cleaning up the pdo_mysql and mysqli documentation
> > - Create a general "The MySQL situation" document that explains the
> > - situation
> >
> > The PHP community has been recommending alternatives for several
> > years now, so hopefully this won't be a new concept or shock to most
> > users
> 
> sounds reasonable and i would love to be not forced loading
> "mysql.so" AND "mysqli.so" because some peopole are using
> legacy code and unwilling to maintain their stuff


Sure, some users in the PHP community are aware of this desire.

We're talking about tons of developers, vast amounts of legacy code
written over 2 decades - longer than many in that same community have
been alive.

Most developers "out there" are not remotely aware of this.

IMHO, it doesn't matter how early the education gets started or how
much time and sugar is used to coat this, it'll be a bitter pill for
a very large group of people.

This needs to be thought out very carefully.

Best Regards,

Mike Robinson