Req #25920 [Opn->Csd]: mssql_connect bad behaviour
| From: | cmb@php.net | Date: | Mon, 08 Jun 2015 22:10:01 +0000 |
| Subject: | Req #25920 [Opn->Csd]: mssql_connect bad behaviour | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-193222@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=25920&edit=1
ID: 25920
Updated by: cmb@php.net
Reported by: morphy at 6deex dot net
Summary: mssql_connect bad behaviour
-Status: Open
+Status: Closed
Type: Feature/Change Request
Package: MSSQL related
Operating System: win2k svr
PHP Version: *
-Assigned To:
+Assigned To: cmb
Block user comment: N
Private report: N
New Comment:
Doesn't the $link_identifier parameter for mssql_query() and
other functions solve the issue?
Anyhow, the Mssql extension has been abandoned as of PHP 5.3.0 in
favor of the SQLSRV extension.
Previous Comments:
------------------------------------------------------------------------
[2003-10-20 06:51:57] morphy at 6deex dot net
Description:
------------
mssql_connect use the same connection id with the same parameters but if i
need different connections to the same machine with the same user but for
different database... im f**ked..
es:
after the second call the $a connection has lost its selected db
Reproduce code:
---------------
<?php
$a = mssql_connect(HOST,USER,PASS);
mssql_select_db(DB1,$a);
$b = mssql_connect(HOST,USER,PASS);
mssql_select_db(DB2,$b);
//after the second call the $a connection has lost
//its selected db
?>
Expected result:
----------------
i expect that $a uses DB1 and $b uses DB2 even if both dbs are in the sama host
Actual result:
--------------
the $a connection loose its own selected db
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=25920&edit=1