Posted: Thu Aug 24, 2006 11:26 am
Compare the various configs, there's bound to be something different. 
A community of PHP developers offering assistance, advice, discussion, and friendship.
http://forums.devnetwork.net/
I researched this issue on google, None of the people having this problem that I found were able to fix it. They were able to supress the errors by turning off mysql.trace_mode.astions wrote:Try setting mysql.trace_mode to off in php.ini.
Why your server has that enabled is a mystery since it is normally turned off. About the only reason to enable that flag in php is to try and track down queries performing table scans and result sets that aren't being freed by the script before execution ends. Basically a way to help tidy up your mysql queries. It shouldn't be enabled except for testing purposes.mysql.trace_mode (boolean)
Trace mode. When mysql.trace_mode is enabled, warnings for table/index scans, non free result sets, and SQL-Errors will be displayed. (Introduced in PHP 4.3.0)