Re: RFC: ext/mysql deprecation
| From: | Rasmus Lerdorf | Date: | Thu, 15 Nov 2012 20:11:43 +0000 |
| Subject: | Re: RFC: ext/mysql deprecation | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-63888@lists.php.net to get a copy of this message | ||
On 11/15/2012 12:08 PM, Will Fitch wrote:
> On Thu, Nov 15, 2012 at 3:00 PM, Rasmus Lerdorf wrote:
> Actually, no it wouldn't. You still get the overhead of the error, plus
> any custom error handlers will be triggered regardless of the
> error_reporting setting which depending on the implementation of the
> error handler can be quite costly performance-wise.
>
> So what solution is there to this? Should it not be deprecated? This
> same issue (is still happening) with register_globals for us, but it's
> acceptable as it has been phased out. Should there be no deprecation
> warning now and wait for a future release?
I'd like to see usage drop off first so we aren't negatively affecting
millions of sites performance-wise, and/or we streamline the error
handling code so there is a way to avoid this performance hit.
-Rasmus