Page 2 of 2

Posted: Thu Aug 24, 2006 11:26 am
by feyd
Compare the various configs, there's bound to be something different. :)

Posted: Thu Aug 24, 2006 12:41 pm
by Benjamin
astions wrote:Try setting mysql.trace_mode to off in php.ini.
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.

Posted: Thu Aug 24, 2006 1:12 pm
by pickle
~astions - I'm going to name my firstborn after you!

It worked great. Thanks.

Posted: Thu Aug 24, 2006 2:08 pm
by AKA Panama Jack
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)
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.

Posted: Fri Aug 25, 2006 3:47 am
by Verminox
If you are using PHP5 just edit the class and add a destructor that calls mysql_free_result() and it will work on all the files using that class. If not, then switch, because its better :)

Edit: Oh, was this solved already? Didn't notice the replies on page 2 >_<

Posted: Fri Aug 25, 2006 9:50 am
by pickle
Thanks for the tip. I had actually thought of that, but we're hard core 4.4.1.