#42544 [Opn]: mssql_select_db changes all open connections OR new_link boolean doesn't work

2007-09-10 Thread fmk
 ID:   42544
 Updated by:   [EMAIL PROTECTED]
 Reported By:  walter at wjd dot nu
 Status:   Open
 Bug Type: Sybase-ct (ctlib) related
 Operating System: linux/debian, linux/ubuntu
 PHP Version:  4.4.7
 New Comment:

When you use the mssql_* functions from the sybase-ct extension, you
should also use the documentation for the sybase_* functions. In this
case the mssql_* functions are aliases for the same functions.

If you want to have all the functions documented (and implemented) for
the mssql extension you should compile PHP using --with-mssql.


Previous Comments:


[2007-09-05 11:25:45] walter at wjd dot nu

So.. I think I've figured it out (I untarred php4-STABLE-200709041230
to have a look). It's a documentation problem and a lacking feature.

I'm to be using the sybase(_ct) package (on debian and ubuntu).
According to apt-cache, this is the standard package for mssql php
support.

This sybase module PHP_FALIAS'es mssql_connect to sybase_connect.
sybase_connect does not take the 'new_link' boolean but a 'charset'
string.

Which leaves me with the two following problems; one documentation
"bug" and one RFE:
- When looking at the mssql_connect manual, I'd like to be informed
that I should be looking at sybase_connect if I'm using sybase_ct.so.
- I'd like a new_link boolean added to sybase_connect :)

Greetings,
Walter Doekes



[2007-09-04 14:31:29] walter at wjd dot nu

Description:

The new_link boolean in mssql_connect does not do what its supposed to
do for me. When select_db'ing the second open link, the first link gets
affected. var_dump tells me that both connections are the same.

When I'm using mssql_pconnect instead of connect, I do get another
resource number for the second connection, but the bug that selects the
wrong database, still remains. 

Is this a wrong version thing? Does mssql_select_db/mssql_query use the
wrong database handle? Does the new_link boolean not work as it should?

I'm lying about the PHP version in the select box; I don't have that
exact version lying around. But I've seen that this bug was dismissed in
March 2006 (http://bugs.php.net/bug.php?id=36639) when there was no
4.4.7.
Latest version I've tested it on, is (I've tested on 4.4.4 as well):

$ php5 -v
PHP 5.1.6 (cli) (built: Jul 17 2007 17:45:52)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies
$ dpkg -l *sybase | grep syb
ii  php5-sybase5.1.6-1ubuntu2.6 Sybase / MS SQL Server module for
php5


Reproduce code:
---


Expected result:

$users: resource(4) of type (sybase-ct link)
$management: resource(5) of type (sybase-ct link)

Success!

Actual result:
--
$users: resource(4) of type (sybase-ct link)
$management: resource(4) of type (sybase-ct link)

Warning: mssql_query(): Sybase:  Server message:  Invalid object name
'LEDEN'. (severity 16, procedure N/A) in /tmp/test.php on line 14

Failed!





-- 
Edit this bug report at http://bugs.php.net/?id=42544&edit=1


#42544 [Opn]: mssql_select_db changes all open connections OR new_link boolean doesn't work

2007-09-05 Thread walter at wjd dot nu
 ID:   42544
 User updated by:  walter at wjd dot nu
 Reported By:  walter at wjd dot nu
 Status:   Open
 Bug Type: Sybase-ct (ctlib) related
 Operating System: linux/debian, linux/ubuntu
 PHP Version:  4.4.7
 New Comment:

So.. I think I've figured it out (I untarred php4-STABLE-200709041230
to have a look). It's a documentation problem and a lacking feature.

I'm to be using the sybase(_ct) package (on debian and ubuntu).
According to apt-cache, this is the standard package for mssql php
support.

This sybase module PHP_FALIAS'es mssql_connect to sybase_connect.
sybase_connect does not take the 'new_link' boolean but a 'charset'
string.

Which leaves me with the two following problems; one documentation
"bug" and one RFE:
- When looking at the mssql_connect manual, I'd like to be informed
that I should be looking at sybase_connect if I'm using sybase_ct.so.
- I'd like a new_link boolean added to sybase_connect :)

Greetings,
Walter Doekes


Previous Comments:


[2007-09-04 14:31:29] walter at wjd dot nu

Description:

The new_link boolean in mssql_connect does not do what its supposed to
do for me. When select_db'ing the second open link, the first link gets
affected. var_dump tells me that both connections are the same.

When I'm using mssql_pconnect instead of connect, I do get another
resource number for the second connection, but the bug that selects the
wrong database, still remains. 

Is this a wrong version thing? Does mssql_select_db/mssql_query use the
wrong database handle? Does the new_link boolean not work as it should?

I'm lying about the PHP version in the select box; I don't have that
exact version lying around. But I've seen that this bug was dismissed in
March 2006 (http://bugs.php.net/bug.php?id=36639) when there was no
4.4.7.
Latest version I've tested it on, is (I've tested on 4.4.4 as well):

$ php5 -v
PHP 5.1.6 (cli) (built: Jul 17 2007 17:45:52)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies
$ dpkg -l *sybase | grep syb
ii  php5-sybase5.1.6-1ubuntu2.6 Sybase / MS SQL Server module for
php5


Reproduce code:
---


Expected result:

$users: resource(4) of type (sybase-ct link)
$management: resource(5) of type (sybase-ct link)

Success!

Actual result:
--
$users: resource(4) of type (sybase-ct link)
$management: resource(4) of type (sybase-ct link)

Warning: mssql_query(): Sybase:  Server message:  Invalid object name
'LEDEN'. (severity 16, procedure N/A) in /tmp/test.php on line 14

Failed!





-- 
Edit this bug report at http://bugs.php.net/?id=42544&edit=1