A little note about multiple simultaneous connections to different hosts...
I work on a site that pulls content primarily from one db but uses a db on a foreign server to verify licensing. One might expect the following to work:
<?php
// Open the connection to the primary db
$res1 = mysql_connect($host1, $user1, $pass1);
mysql_select_db($db1);
// Open connection to the license server
$res2 = mysql_connect($host2, $user2, $pass2);
mysql_select_db($db2, $res2);
// Pull license data and close when done
mysql_query($check_sql, $res2);
// ...
mysql_close($res2);
// Now pull content from the primary db
// Not specifying the resource should default to the last open db
mysql_query($query);
// ...
?>
Turns out this last query, since it cant find an active connection, will try to connect with mysql_connect() with no paramaters. But if instead you do it as mysql_query($query, $res1), or alternatively, run the mysql_connect for this host again then it works fine. Thus, it doesnt seem to be possible to have code with an overarching "global" db connection interspersed with temporary connections to another host/db....
mysql_close
(PHP 4, PHP 5)
mysql_close — MySQL 접속을 닫음
설명
bool mysql_close
([ resource
$link_identifier
] )
mysql_close()는 link_identifier와
연관된 MySQL서버의 비영속적 접속을 종료한다.
link_identifier가 기술되지 않으면 최근 접속된 연결을 사용한다.
mysql_close()는 비영구적으로 열려진 링크에서는 일반적으로 스크립트 실행 마지막 부분에서 자동으로 종료되므로 사용할 필요가 없다. resource 해제하기.
인수
-
link_identifier -
MySQL 연결. 지정하지 않으면 mysql_connect()로 연 마지막 연결을 사용합니다. 연결이 없으면, 인수 없이 mysql_connect()를 호출하여 연결을 만듭니다. 연결이 성립되지 않으면
E_WARNING등급의 오류를 생성합니다.
반환값
성공 시 TRUE를, 실패 시 FALSE를 반환합니다.
예제
Example #1 mysql_close() 예제
<?php
$link = mysql_connect('localhost', 'mysql_user', 'mysql_password');
if (!$link) {
die('Could not connect: ' . mysql_error());
}
echo 'Connected successfully';
mysql_close($link);
?>
위 예제의 출력:
Connected successfully
주의
Note:
mysql_close()는 mysql_pconnect()에 의해 영속적으로 연결된 접속은 종료하지 않는다.
add a note
User Contributed Notes 6 notes
bbodelcampo at yahoo dot co dot uk ¶
18 years ago
beer_nomaed _AT_ hotmail _DOT_ com ¶
19 years ago
Be careful when using multiple links to connect to same database (with same username). Unless you specify explicitly in mysql_connect() to create a new link, it will return an already open link. If that would be closed by mysql_close(), it will also (obviously) close the other connection, since the link is the same.
Had lot of trouble figuring it out, since in <=4.3.6 there was a bug which didn't close the connection, but after the patch to >=4.3.7, all my application broke down because of a single script that did this.
mdes[SPAM]saintes at gmail dot com ¶
13 years ago
i just came over a problem that i had with apache.
It crashs and said :
"Parent: child process exited with status 3221225477 -- Restarting."
the error came from the extesion php_mysql.dll
i didn't understand what was the reason of that crash..
Then, i debug the script that i had downloaded and i noticed that that was the function mysql_close() which caused the problem.
The solution is, to send to it the link identifier which is optionnal in the description but cause a crash with no commentary.
Thanks to agneady.
Anonymous ¶
14 years ago
At least with PHP5.3.2 and Windows connecting by tcp, you should always use this mysql_close() function to close and free up the tcp socket being used by PHP. Garbage collection after script execution does not close the tcp socket on its own. The socket would otherwise remain in 'wait' state for approximately 30 seconds, and any additional page loads/connection attempts would only add to the total number of open tcp connections. This wait time does not appear to be configurable via PHP settings.
levi at alliancesoftware dot com dot au ¶
18 years ago
As at 5.0.x and 4.3.x: This function should never be used with shared links; instead you should set your link variables to null.
(This explains red's and beer's () problems in previous comments)
Here is how shared links work:
- Each link is a resource. mysql_connect() by default looks for a resource with the same paramaters. If one exists, it will return the existing resource.
- Every assignment of that resource to a variable increases the resource's reference count.
- When the reference is decremented to zero, the underlying TCP/socket connection is closed.
- Every assignment of a variable away from that resource decrements the reference count. (This includes a function level variable going out of scope)
- mysql_close() also decrements the reference count.
Note the last two points: mysql_close() _and_ reassignment of a variable decrement the link's reference count.
A common mistake is a function like:
<?php
function dothings() {
$link = mysql_open(...);
// .. do some queries ..
mysql_close($link)
$link = null;
}
?>
this will decrement the counter twice, possibly closing the underlying connection and causing errors in other parts of the program.
http://bugs.php.net/bug.php?id=30525 "this is not a bug but just how it works"
omega99999 at gmail dot com ¶
13 years ago
The variable is definitely not optional in 5.3... Caused me a bit of a headache when I was debugging until I realized it was the close function that was causing a hang. So if using just:
<?php
mysql_connect(<...>);
mysql_close();
?>
Use:
<?php
$connection = mysql_connect(<...>);
mysql_close($connection);
?>
(where $connection is any variable of your choice)
