Bug #1245: odbc_exec fails, odbc_prepare/odbc_execute work
| From: | andrew dot macintyre at aba dot gov dot au | Date: | Thu, 18 Mar 1999 07:24:52 +0000 |
| Subject: | Bug #1245: odbc_exec fails, odbc_prepare/odbc_execute work | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-4676@lists.php.net to get a copy of this message | ||
From: andrew.macintyre@aba.gov.au
Operating system: FreeBSD 2.2.7-Release
PHP version: 3.0.6
PHP Bug Type: ODBC related
Bug description: odbc_exec fails, odbc_prepare/odbc_execute work
Apache-1.3.4+PHP-3.0.6 port taken from FreeBSD ports, modified to configure with
"-with-openlink". Openlink MT driver library (BSDI 2.1version) statically linked without
the iODBC driver manager. RDBMS server is Ingres 6.4(05). PHP also configure with PostgreSQL and
the font support.
Having successfully connected to the Ingres database & successfully issued a "set lockmode
...." statement using odbc_exec(), issuing a simple select of the form "select key, value
from table" via:
1) odbc_exec() - fails with "Syntax error or access violation" [ODBC state 37000].
2) odbc_prepare()/odbc_execute() - works correctly.
To confirm, I built the test program from the iODBC v2.50 driver manager suite, and linked in the
Openlink driver the same way as for PHP, and the same select was issued and returned the correct
result, ie the same as the result obtained from the _prepare/_execute sequence above.
I note from bug #835 that there are/were differences in behaviour between the two SQL execution
techniques when the Openlink drivers are involved.
--
PHP Development Mailing List http://www.php.net/
To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net
For help: php-dev-help@lists.php.net