Re: PHP 4.0 Bug #3976: mysql_query produces warnings (fwd)

Hi! >>>>> "Zeev" == Zeev Suraski <zeev@zend.com> writes: Zeev> On Thu, 30 Mar 2000, Michael Widenius wrote: >> >>>>> "Andi" == Andi Gutmans <andi@zend.com> writes: >> Andi> Guys, Andi> Since we have incorporated the MySQL client library it seems like we have Andi> had a lot more problems with MySQL. Andi> People often have problems when using mod_auth_mysql (compiled against a Andi> different version of the MySQL client library) and mod_php with the same Andi> Apache server. Andi> I don't know what the exact problem these guys seem to be encountering but Andi> it seems that when they link against a different mysql client library Andi> things start working again. >> Andi> What do you guys think? >> Andi> Andi >> >> What kind problems do the get? Has anyone been able to reproduce this >> in any way? Zeev> There've been several people that appeared to be having problems with Zeev> mysql_store_result() failing. As I never got to see the warning message I Zeev> put into the PHP MySQL module almost 3 years ago (about failing to store Zeev> the MySQL result) until about 2 weeks ago, I think it ought to be related Zeev> to this bundling issue. Zeev> Do you think it can be related to the threading issue in any way? Or the Zeev> SIGPIPE? I have recently got some bug reports when linking Apache with a threadsafe version of libmysql.c (I don't know the exact reason for this yet). I got myself a problem with SIGPIPE a couple of days ago and the suggested patch fixes it. I think it's best to do next release without the SIGPIPE hack and without threads (if possible) just to check if this solves this! Regards, Monty