|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2003-03-11 23:34 UTC] sniper@php.net
[2003-03-11 23:54 UTC] craigs at abr dot com dot au
|
|||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Thu Oct 30 18:00:02 2025 UTC |
Calling mysql_errno or mysql_error after a failed mysql_connect when there is an already existing mysql connection resource does not return any error message for the failed connect. According to the doco, it would be expected to return an error such as 'Unknown Mysql Server Host'. I have searched the bug database, and bugs 2051 and 10291 report a related issue of mysql_error/errno not reporting mysql_connect errors, however a review of the change log reports support for mysql_connect errors was added in 4.0.6. A code segment that reproduces this bug follows ======================== $LinkID = mysql_connect("localhost","login","password"); mysql_select_db("mysql"); mysql_query("SELECT * FROM user"); $LinkID2 = mysql_connect("badserver","login","password"); echo "Mysql Error: ".mysql_errno()." - ".mysql_error()."\n"; ================== Expected result- Mysql Error: 2005 - Unknown MySQL Server Host 'badserver' (1) Actual Result - Mysql Error: 0 - Commenting out the first 3 lines and re running the script returns the expected error of unknown server. I would guess that the mysql_error functions use of a default link resource of the last open resource is at fault, as none is opened in the connect. Cheers Craig