Re[4]: [PHP-DEV] Major Bug in multiple MySQL Connections?

From: Date: Mon, 22 Apr 2002 18:23:58 +0000
Subject: Re[4]: [PHP-DEV] Major Bug in multiple MySQL Connections?
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-83161@lists.php.net to get a copy of this message
I'd rather have people understand what they are doing than build that into the low-level db functions. That sort of stuff belongs in user space. -Rasmus On Mon, 22 Apr 2002, Daniel Lorch wrote: > hi, > > because this is causing troubles to many users. > > $con1 = mysql_connect(..); > $con2 = mysql_connect(..); > > mysql_select_db($con1, "db1"); > mysql_select_db($con2, "db2"); > > mysql_query("SELECT * FROM ..", $con1); /* this is applied to 'db2'. > or am I wrong? */ > > The current DB should be part of the mysql handle. Also the mysql > result set (I remember my db-classes to use each others result sets). > > -daniel > > ----- Original Message ----- > >From : Rasmus Lerdorf [mailto:rasmus@lerdorf.ca] > Sent : Montag, 22. April 2002 > Subject: [PHP-DEV] Major Bug in multiple MySQL Connections? > > > Because the current db is not a property specified in mysql_connect() so I > > don't see what you would be switching back and forth from/to. > > > -Rasmus > >

« previous php.dev (#83161) next »