#30592 [Bgs]: not a valid MySQL-Link resource

From: Date: Thu, 28 Oct 2004 22:07:25 +0000
Subject: #30592 [Bgs]: not a valid MySQL-Link resource
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-68454@lists.php.net to get a copy of this message
ID: 30592 Updated by: derick@php.net Reported By: v_shiray at ukr dot net Status: Bogus Bug Type: MySQL related Operating System: Linux PHP Version: 4.3.9 New Comment: And this is NOT a bug. You're doing something wrong here, ask on php-general@lists.php.net about it. This bug system is not a forum. Previous Comments: ------------------------------------------------------------------------ [2004-10-28 20:03:07] v_shiray at ukr dot net Hmm. I did not say ANYTIME about opening a new link to MySQL. It's very strange that you take care on this. Please reread my initial submission. I noticed about a possible 'bug' with resource freeing. Provided source will work perfectly if I will comment next line: // $db2 = 0; It's a very strange 'behaviour' as for me! Do you think on other ? ------------------------------------------------------------------------ [2004-10-28 19:03:56] radical@php.net If you want to open a new link to a MySQL server you must specify the 4th param to mysql_connect witch is a boolean that has a default value of FALSE. $link_1 = mysql_connect('host', 'user', 'pass'); $link_2 = mysql_connect('host', 'user', 'pass', TRUE); Only this is the way to create a new link to MySQL... otherwise PHP will just return the old one... but only if mysql_connect's parrams are the same ! This 4th param was introduced as of PHP 4.2.0. To work on the $link_1 you should specify it... mysql_query("SELECT ...", $link_1); because otherwise PHP will use $link_2... akka the last opened link ! Good fortune ! I hope it's clear ! ------------------------------------------------------------------------ [2004-10-28 18:36:30] v_shiray at ukr dot net I had read manual many time before submitinig the "bug". So as you said it's a normal behavior but it's very strange as for me. Maybe you will have time to answer on some questions. Why do this behaviour different between versions of PHP, e.g 4.3.6 and 4.3.9 ? How can I unset $db2 without triggering this "problem"? So I may change $db2 = 0; to unset($db2); with the same effect. ------------------------------------------------------------------------ [2004-10-28 07:22:01] georg@php.net Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php See http://www.php.net/mysql_connect ------------------------------------------------------------------------ [2004-10-28 03:01:18] v_shiray at ukr dot net MySQL 4.0.20 Problem has been detected also with PHP 4.3.8 and 5.0.2 on the same computer RedHat 9.0, MySQL 3.23.58, PHP 4.3.9 ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/30592 -- Edit this bug report at http://bugs.php.net/?id=30592&edit=1

« previous php.bugs (#68454) next »