#39453 [Fbk->Opn]: Misleading note in ODBC Functions (Unified)
| From: | nick dot gorham at easysoft dot com | Date: | Tue, 14 Nov 2006 09:35:38 +0000 |
| Subject: | #39453 [Fbk->Opn]: Misleading note in ODBC Functions (Unified) | ||
| References: | 1 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969374394@lists.php.net to get a copy of this message | ||
ID: 39453
User updated by: nick dot gorham at easysoft dot com
Reported By: nick dot gorham at easysoft dot com
-Status: Feedback
+Status: Open
Bug Type: Documentation problem
PHP Version: Irrelevant
New Comment:
I see the note on the top of the page here.
http://uk.php.net/manual/en/ref.uodbc.php
"we can't possible accommodate users who don't set permissions properly
(and decide to rebuild PHP)."
Ok, thats always your decision, but the problem I see in this case is
its the note that was the reason the user "decided" to rebuild PHP, as
it gave the indication that to do what he wanted to do, a rebuild was
required replacing unixODBC with iODBC
Previous Comments:
------------------------------------------------------------------------
[2006-11-11 18:08:40] sean@php.net
Which note do you mean? The note I see doesn't say the same thing you
indicate, but I might be just missing it.
Also, while your documentation problem may be justified, we can't
possible accommodate users who don't set permissions properly (and
decide to rebuild PHP).
------------------------------------------------------------------------
[2006-11-09 17:14:27] nick dot gorham at easysoft dot com
Description:
------------
On the Unified ODBC doc page, there is a note at the top that indicates
that iODBC is the way to use ODBC via PHP. The problem with this (IMHO),
is that it seems to be suggesting that iODBC is the only way. Of course
unixODBC is still supported in the build, and last time I looked that
was what most linux distribs came with.
I have just had a user, causing himeself all sorts of problems, as he
decided he needed to rebuild his copy of PHP because it was supplied
built with unixODBC, and he needed to change to iODBC. That wasn't his
problem at all, it was actually a permissions problem.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=39453&edit=1