Bug #12985 Updated: mysql_connect() forces reuse of the connection
| From: | mfischer@php.net | Date: | Tue, 28 Aug 2001 09:03:05 +0000 |
| Subject: | Bug #12985 Updated: mysql_connect() forces reuse of the connection | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-64480@lists.php.net to get a copy of this message | ||
ID: 12985
Updated by: mfischer
Reported By: vedad@kajtaz.net
Status: Open
Bug Type: Feature/Change Request
Operating System: not os related
PHP Version: 4.0.4pl1
New Comment:
Vedad,
I had exactly the same issue back a few months. Actually I made such a patch and sent it to Zeev,
unfortunately he didn't included it. And, you're right, the patch is trivial.
- Markus
Previous Comments:
------------------------------------------------------------------------
[2001-08-27 22:47:02] joey@php.net
Nevermind...I read this whole report backwards. I thought
you were looking for persistence, not trying to get rid
of it. Apologies.
------------------------------------------------------------------------
[2001-08-27 22:45:59] joey@php.net
What is different between what you are asking for
and mysql_pconnect()?
http://www.php.net/msyql-pconnect
------------------------------------------------------------------------
[2001-08-27 20:47:11] vedad@kajtaz.net
Hi all,
i've just discovered that mysql_connect() uses a hash that forces it to reuse a connection on a
second call to mysql_connect() with the same arguments, instead of opening a new connection.
This was, at least for me, an unexpected behaviour: i was hoping to be able to use several database
connections to the same mysql server (and same user) in order to be able to issue several LOCK TABLE
or GET_LOCK() queries (mysql allows only one 'active' lock per connection)
[I know basic locking may be done on php server's system level, but it doesn't make sense
in web-cluster environment, and using a database to centralize locks sounds interesting]
I also took a look into php's mysql api source (i'm not familiar with php sources), and
adding an optional argument saying _not_ to reuse a connection or coding an alternative
mysql_connect() from the existing one doesnt _seem_ to be a long or complicated task.
I _might_ do the change myself for my server, but as the sites i'm working on are unlikely to
be hosted on my server, this is not very portable and would be probably useless.
Please tell me what you think about this issue, and if a change to mysql_connect() function is
conceivable (in that case i'd be glad to do the change myself and send you the result :)
Thanks
-- vedad
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=12985&edit=1