php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #29366 Change in error_reporting behavior
Submitted: 2004-07-24 21:11 UTC Modified: 2004-08-08 15:05 UTC
Votes:2
Avg. Score:3.5 ± 0.5
Reproduced:2 of 2 (100.0%)
Same Version:2 (100.0%)
Same OS:2 (100.0%)
From: nbi at gmx dot de Assigned:
Status: Not a bug Package: PHP options/info functions
PHP Version: 4.3.8 OS: Windows XP
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: nbi at gmx dot de
New email:
PHP Version: OS:

 

 [2004-07-24 21:11 UTC] nbi at gmx dot de
Description:
------------
There seems to be a change in error_reporting(), that came up from PHP 4.3.6 to 4.3.7:

Setting error_reporting(0) did NOT display a warning like 
Warning: mysql_query(): Your query requires a full tablescan (table xyz, 4 rows affected). Use EXPLAIN to optimize your query. in xyz.php on line 594

With PHP 4.3.7 and 4.3.8 this warning is displayed, despite settings of error_reporting(0) or ini_set ('error_reporting', 0)



Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2004-07-27 23:45 UTC] evan at fusion-zero dot com
In php.ini, you probably have mysql.trace.mode set to On
You need to set it to Off, just like this.

; Trace mode. When trace_mode is active (=On), warnings for table/index scans and
; SQL-Erros will be displayed.
mysql.trace_mode = Off
 [2004-07-28 23:21 UTC] nbi at gmx dot de
Yes, indead: mysql.trace_mode = Off solved the problem.
However, mysql.trace_mode could be ON up to PHP 4.3.6 without having any apparent effect, though.
Thanks for your help.
 [2004-08-08 15:05 UTC] magnus@php.net
Not a bug. 
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Wed Sep 11 19:01:27 2024 UTC