ID: 14478
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Closed
Bug Type: MySQL related
Operating System: FreeBSD
PHP Version: 4.0.6
New Comment:
sorry about that... I overlooked this behavior in the docs.
but I still think that this behavior is counter-intuitive
since it's perfectly reasonable to want to have connections
to multiple databases on the same host with the same
credentials... I'll check it out from CVS and give it a
whirl.
Thanks for looking at it so quickly, though!
Previous Comments:
------------------------------------------------------------------------
[2001-12-13 00:42:29] [EMAIL PROTECTED]
Not bogus :) This is a feature request and has already been done a short time ago.
------------------------------------------------------------------------
[2001-12-13 00:40:59] [EMAIL PROTECTED]
Thank you for your report. However, please review the
documentation before submitting a bug report - this is the
intentional and expected behavior.
------------------------------------------------------------------------
[2001-12-13 00:39:53] [EMAIL PROTECTED]
This is/was an intended behaviour. There's a new expiremental optional parameter to
mysql_connect() in CVS which allows you to force to create new resource rather than
reuse existing ones, e.g.:
$con1 = mysql_connect('foo','bar','baz');
$con2 = mysql_connect('foo','bar','baz', true);
Will result in $con2 being a new resource, not the same again.
Closing.
------------------------------------------------------------------------
[2001-12-12 21:21:00] [EMAIL PROTECTED]
I've noticed what appears to be a bug in the
mysql_connect() and mysql_pconnect() (or perhaps the mysql
client libraries): multiple calls to either function with
identical arguments return the same resource id, preventing
me from connecting to multiple databases on the same host,
with the same credentials. Example:
<?php
$conn1 = mysql_connect('host','username','pass');
$conn2 = mysql_connect('host','username','pass');
echo "conn1: $conn1\n";
echo "conn2: $conn2\n";
?>
Produces:
conn1: Resource id #1
conn2: Resource id #1
If I then issue a call to mysql_select_db('foo',$conn1),
'foo' also becomes the active database on $conn2 since the
handles point to the same resource. Doesn't this contradict
the idea of having separate connection handles? Or is it a
short-coming of the client libraries?
Thanks!
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=14478&edit=1
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
