#42544 [NoF->Opn]: mssql_select_db changes all open connections OR new_link boolean doesn't work
| From: | walter at wjd dot nu | Date: | Sat, 22 Nov 2008 22:28:10 +0000 |
| Subject: | #42544 [NoF->Opn]: mssql_select_db changes all open connections OR new_link boolean doesn't work | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-1535@lists.php.net to get a copy of this message | ||
ID: 42544
User updated by: walter at wjd dot nu
Reported By: walter at wjd dot nu
-Status: No Feedback
+Status: Open
Bug Type: Documentation problem
Operating System: linux/debian, linux/ubuntu
PHP Version: 4.4.7
New Comment:
How is that no feedback? Did I forget to tick a box?
Previous Comments:
------------------------------------------------------------------------
[2008-11-18 01:00:01] doc-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
[2008-11-11 22:11:29] walter at wjd dot nu
I'm sorry. I didn't think my comments left that much room for
interpretation. I'll go very very slow:
1) noob user installs php and sybase_ct (because his package manager
tells him that that's the way to connect to MS-SQL databases)
2) noob user looks for mssql functions
3) noob user finds mssql_* functions that seem to work, except for the
mssql_connect function's fourth parameter which looks like its broken.
4) but wait, it is not broken. noob user is looking in the wrong
place.
I don't know who came up with the FALIAS'ing of mssql_* to sybase_* in
the sybase_ct module. But the fact that the mssql_* functions do not do
what they advertise means that (1) either sybase_ct is broken because it
implements documented functionality in the wrong way or that (2) the
documentation is wrong.
The simplest fix is a big red warning sign on the mssql_connect page
that says: """Hey noob! If you have sybase_ct.so in your php.ini, you're
should be loooking at sybase_connect."""
------------------------------------------------------------------------
[2008-11-10 11:15:29] vrana@php.net
Please specify what exactly should be documented.
------------------------------------------------------------------------
[2007-09-10 16:24:55] fmk@php.net
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.
------------------------------------------------------------------------
[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
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/42544
--
Edit this bug report at http://bugs.php.net/?id=42544&edit=1