Re: RFC: ext/mysql deprecation
| From: | Will Fitch | Date: | Thu, 15 Nov 2012 19:53:24 +0000 |
| Subject: | Re: RFC: ext/mysql deprecation | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-63884@lists.php.net to get a copy of this message | ||
On Thu, Nov 15, 2012 at 2:48 PM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:
> Hi!
>
> > Again, though, this is a long way down the road: today's discussion is
> > purely about deprecation.
>
> So these people using mysql-based code will have for years to live with
> applications generating thousands of warnings and not be able to do a
thing about it? How is it good for them?
>
I don't mean to state the obvious, but wouldn't display_errors = 'Off' in
production or error_reporting = E_ALL ^ E_DEPRECATED be sufficient? This
is the same approach taken with register_globals - and it happened between
5.3 and 5.4.
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>