issue.)
Matthew Walker
Senior Software Engineer
ePliant Marketing
-Original Message-
From: Markus Fischer [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 22, 2002 6:50 AM
To: Matthew Walker
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] Major Bug
I believe I may have found a major bug in the use of multiple MySQL
connections. Please see my bug report at HYPERLINK
http://bugs.php.net/bug.php?id=16730http://bugs.php.net/bug.php?id=167
30. If Im wrong about this, please tell me how to fix it. This is a
showstopper bug for the software Im
] Major Bug in multiple MySQL Connections?
I believe I may have found a major bug in the use of multiple MySQL
connections. Please see my bug report at HYPERLINK
http://bugs.php.net/bug.php?id=16730http://bugs.php.net/bug.php?id=167
30. If Im wrong about this, please tell me how to fix
Hello,
this is not a bug, see the details in the bugreport.
Derick
On Mon, 22 Apr 2002, Matthew Walker wrote:
I believe I may have found a major bug in the use of multiple MySQL
connections. Please see my bug report at HYPERLINK
AM
To: Matthew Walker
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] Major Bug in multiple MySQL Connections?
Hello,
this is not a bug, see the details in the bugreport.
Derick
On Mon, 22 Apr 2002, Matthew Walker wrote:
I believe I may have found a major bug in the use of multiple MySQL
Hello Matthew,
you should read my commect on this bug report too. 4.2.0
which will be released soon contains already a workaround for
this limitation.
- Markus
On Mon, Apr 22, 2002 at 06:41:44AM -0600, Matthew Walker wrote :
I believe I may have found a major bug in the
.)
Matthew Walker
Senior Software Engineer
ePliant Marketing
-Original Message-
From: Markus Fischer [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 22, 2002 6:50 AM
To: Matthew Walker
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] Major Bug in multiple MySQL Connections?
Hello Matthew
Walker
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] Major Bug in multiple MySQL Connections?
Hello Matthew,
you should read my commect on this bug report too. 4.2.0
which will be released soon contains already a workaround for
this limitation.
- Markus
On Mon, Apr 22
Software Engineer
ePliant Marketing
-Original Message-
From: Rasmus Lerdorf [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 22, 2002 5:53 AM
To: Matthew Walker
Cc: Markus Fischer; [EMAIL PROTECTED]
Subject: RE: [PHP-DEV] Major Bug in multiple MySQL Connections?
Just curious, why do you
-Original Message-
From: Rasmus Lerdorf [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 22, 2002 5:53 AM
To: Matthew Walker
Cc: Markus Fischer; [EMAIL PROTECTED]
Subject: RE: [PHP-DEV] Major Bug in multiple MySQL Connections?
Just curious, why do you need multiple identical connections
Senior Software Engineer
ePliant Marketing
-Original Message-
From: Markus Fischer [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 22, 2002 6:50 AM
To: Matthew Walker
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] Major Bug in multiple MySQL Connections?
Hello
But in this case he wanted to connect twice with the same credentials so
that argument makes no sense.
-Rasmus
On Mon, 22 Apr 2002, Georg Richter wrote:
On Monday, 22. April 2002 14:07, Rasmus Lerdorf wrote:
But changing the active DB on an open connection is a trivial operation in
MySQL.
Software Engineer
ePliant Marketing
-Original Message-
From: Markus Fischer [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 22, 2002 6:50 AM
To: Matthew Walker
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] Major Bug in multiple MySQL Connections?
Hello
I epected that what we refer to as 'small, self-contained'
example, for which most of them don't make sense :p
On Mon, Apr 22, 2002 at 05:40:31AM -0700, Rasmus Lerdorf wrote :
But in this case he wanted to connect twice with the same credentials so
that argument makes no sense.
:[EMAIL PROTECTED]]
Sent: Monday, April 22, 2002 6:50 AM
To: Matthew Walker
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] Major Bug in multiple MySQL Connections?
Hello Matthew,
you should read my commect on this bug report too. 4.2.0
which will be released
, 2002 6:50 AM
To: Matthew Walker
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] Major Bug in multiple MySQL Connections?
Hello Matthew,
you should read my commect on this bug report too. 4.2.0
which will be released soon contains already a workaround
At 17:27 22-4-2002, Rasmus Lerdorf shared with all of us:
The proper way to do this in your generalized app would be to either force
a mysql_select_db on each query to make sure you are talking to the right
one, or if you prefer do a select database() query to see which is the
current one.
???
Hi,
No, it doesn't satisfy me at all. Your application design is broken and
forcing multiple identical connections doesn't solve it at all. You are
trying to associate a selected DB with a database connection artificially.
a couple of years ago I was using PHPLIBs db-class and my own
It's not a silly behaviour. Database connections are a very limited
resource, much more so than open files, and time after time we saw code
that would open up multiple identical connections for no reason
whatsoever. This is especially true of large apps that are able to swallow
other apps. Like
]: [PHP-DEV] Major Bug in multiple MySQL Connections?
It's not a silly behaviour. Database connections are a very limited
resource, much more so than open files, and time after time we saw code
that would open up multiple identical connections for no reason
whatsoever. This is especially true of large
To: Daniel Lorch
Cc: Markus Fischer; Matthew Walker; [EMAIL PROTECTED]
Subject: Re[2]: [PHP-DEV] Major Bug in multiple MySQL Connections?
It's not a silly behaviour. Database connections are a very limited
resource, much more so than open files, and time after time we saw code
that would open up
PROTECTED]]
Sent : Montag, 22. April 2002
Subject: [PHP-DEV] Major Bug in multiple MySQL Connections?
It's not a silly behaviour. Database connections are a very limited
resource, much more so than open files, and time after time we saw code
that would open up multiple identical connections
on and if needed, switch back -
transparently to the user? The current implementation only confuses
people.
-daniel
- Original Message -
From : Rasmus Lerdorf [mailto:[EMAIL PROTECTED]]
Sent : Montag, 22. April 2002
Subject: [PHP-DEV] Major Bug in multiple MySQL Connections
On Mon, Apr 22, 2002 at 07:19:48PM +0200, Melvyn Sopacua wrote :
At 17:27 22-4-2002, Rasmus Lerdorf shared with all of us:
The proper way to do this in your generalized app would be to either force
a mysql_select_db on each query to make sure you are talking to the right
one, or if you
Or use a simple database wrapper, that will save you coding time anyway.
Try PHPLIB's wrappers, for example. They handle doing the database select
for you, you just have to do the query.
Rasmus Lerdorf wrote:
So use mysql_db_query()
On Mon, 22 Apr 2002, Matthew Walker wrote:
Since
: Re[2]: [PHP-DEV] Major Bug in multiple MySQL Connections?
Or use a simple database wrapper, that will save you coding time anyway.
Try PHPLIB's wrappers, for example. They handle doing the database
select
for you, you just have to do the query.
Rasmus Lerdorf wrote:
So use mysql_db_query
this sounds reasonable. But why don't the connection aliases keep
the current db they are working on and if needed, switch back -
transparently to the user? The current implementation only confuses
people.
Try dbx, it does exactly that...
Cheerio, Mc.
--
PHP Development Mailing List
? */
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:[EMAIL PROTECTED]]
Sent : Montag, 22. April 2002
Subject: [PHP-DEV] Major Bug in multiple
db-classes to use each others result sets).
-daniel
- Original Message -
From : Rasmus Lerdorf [mailto:[EMAIL PROTECTED]]
Sent : Montag, 22. April 2002
Subject: [PHP-DEV] Major Bug in multiple MySQL Connections?
Because the current db is not a property specified
29 matches
Mail list logo
