Re: PHP 4.0 Bug #9397 Updated: odbc_setoption() cannot accept string value (patch included)
| From: | Jeffrey Lin | Date: | Fri, 23 Feb 2001 06:37:00 +0000 |
| Subject: | Re: PHP 4.0 Bug #9397 Updated: odbc_setoption() cannot accept string value (patch included) | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-47323@lists.php.net to get a copy of this message | ||
Dear kara,
I am sorry for not specifying it clearly last time. SQL_EXTENSION_NAME is
used
specifically for our database, DBMaker.
We are developers for this database and we have also have developed php
driver for our database. Because of some specific features of our database,
we really need to let users who use our database be able to set this
kind of options. Unfortunately, ODBC 2.x does not allow setting attributes
with string-type values.
Since the ODBC version currently used in php is, as you can see from the
source code, 2.x. We really cannot use SQLSetStmtAttr() provided by
ODBC 3.
We didn't use HAVE_DBMAKER ifdefs because we think other databases
might be glad to see this, too.
kara@php.net ¼¶¼g©ó¤å³¹ <20010222163525.28452.qmail@php2.chek.com>...
>ID: 9397
>Updated by: kara
>Reported By: clin@lion.syscom.com.tw
>Old-Status: Open
>Status: Feedback
>Bug Type: ODBC related
>Assigned To:
>Comments:
>
>In ODBC 2.x it is not possible to pass string values to
>SQLSetStmtOption(). It is possible with ODBC 3,
>SQLSetStmtAttr() has an additional parameter to specify the
>string length.
>By the way: I couldn't find SQL_EXTENSION_NAME as possible
>attribute to SQLSetStmtAttr(). What's it's pupose?
>