Thanks everyone for all the help. I found the problem. It has to do
with a bug in my error handler class that my script loaded prior to
executing mysql_connect(). Once I removed the error handler class,
mysql_connect() started to behave as expected. My bad.
Tom
On Sun, 30 Jan 2005 01:16:10 -060
tom soyer wrote:
Thanks for the error handling code. I think PHP still has a basic
problem. If mysql sever connection times out because wrong username or
password was used, then mysql_connect() should return FALSE. But this
is not the case, why? Is it possible that mysql_connect() could not
read th
tom soyer wrote:
> Thanks for the error handling code. I think PHP still has a basic
> problem. If mysql sever connection times out because wrong username or
> password was used, then mysql_connect() should return FALSE.
It does, at least for me on PHP 4.3.10 connecting to a local MySQL 4.0.23
ser
Thanks for the error handling code. I think PHP still has a basic
problem. If mysql sever connection times out because wrong username or
password was used, then mysql_connect() should return FALSE. But this
is not the case, why? Is it possible that mysql_connect() could not
read the "connection fai
On 29 Jan 2005 tom soyer wrote:
> I tried mysql_connect() function, and it won't reture FALSE if
> connection failed. Instead, the script times out after 30 seconds and
> displays an Fatal error message "Maximum execution time of 30 seconds
> exceeded".
I think the issue here is if the server do
Hi,
I tried mysql_connect() function, and it won't reture FALSE if
connection failed. Instead, the script times out after 30 seconds and
displays an Fatal error message "Maximum execution time of 30 seconds
exceeded". For example:
mysql_connect(' ',' '); returns TRUE because mysql logs in the use
6 matches
Mail list logo
