#29366 [Opn->Csd]: Change in error_reporting behavior

ID: 29366 User updated by: nbi at gmx dot de -Summary: Change in error_reporting behavier Reported By: nbi at gmx dot de -Status: Open +Status: Closed Bug Type: PHP options/info functions Operating System: Windows XP PHP Version: 4.3.8 New Comment: 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. Previous Comments: ------------------------------------------------------------------------ [2004-07-27 23:45:59] 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-24 21:11:59] 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) ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=29366&edit=1