Re: 4.1.0RC5 -- mysql_select_db() ?

If it was reported for an earlier version, then it's going to stay in 4.1.0 and not going to stop it... We can't hold a release for things like that, there are probably hundreds of bugs in that level in PHP. The show goes on! Zeev At 19:36 03/12/2001, Hellekin O. Wolf wrote:

Derick and Zak will be happy, Zeev not so much... When you open 2 connections using mysql_pconnect(), although 2 resources are created, only one is taken into account. It seems that the second argument of mysql_select_db() is not taken into account. Instead, the last chosen db is used. I understand this for non-persistent connections, as the last open one is always taken. But for pconnect(), as it creates a different resource -- at least it says so -- db handlers should be taken. I browsed the manual for persistent connections and mysql_pconnect(). For the latter we have : "First, when connecting, the function would first try to find a (persistent) link that's already open with the same host, username and password. If one is found, an identifier for it will be returned instead of opening a new connection." This has been reported for earlier versions but I didn't find a suitable bug report. Also, the documentation seems confusing to me about the real behavior of pconnect. As I understand it, either the same resource ID should be returned, or a different one -- as it seems to be now -- should be fully honored. You can see an example at http://php.hellekin.com/test/test-mysql_dual_connect.php hellekin -- PHP Quality Assurance Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-qa-unsubscribe@lists.php.net For additional commands, e-mail: php-qa-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net