ID: 20203
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: ODBC related
Operating System: sparc solaris 2.8 and 2.6
PHP Version: 4.2.3
New Comment:
Hello from Athens AGAIN
WOWOWOWOWOW I am happy
I removed the line you said from ext/odbc/php_odbc.h
and DAMN it works !!!!!!!!!!!!!
Thanks very much for your help
I anyway think that the bug still exists as fat as SQLExtendedFetch is
conserned and has to be resolved in future releases of php (I used
4.2.3)
Best regards
Christos
Previous Comments:
------------------------------------------------------------------------
[2002-11-18 08:39:51] [EMAIL PROTECTED]
Hello again
You mean the file ext/odbc/php_odbc.h ??
By the way the openlink "odbctest" program works with SQLFetch and not
with SQLExtendedFetch
Best Regards
Christos
------------------------------------------------------------------------
[2002-11-18 07:13:23] [EMAIL PROTECTED]
What you're asking is an evil thing, but here goes:
In the php_odbc_includes.h file remove the line HAVE_EXTENDED_FETCH
from the HAVE_IODBC section of code.
Problem is iODBC does work with SQLExtendedFetch.
------------------------------------------------------------------------
[2002-11-18 07:11:37] [EMAIL PROTECTED]
As with everything OpenSource, gcc. :)
------------------------------------------------------------------------
[2002-11-18 06:31:48] [EMAIL PROTECTED]
I did some further investigation and discovered that odbctest (always
succesfull) uses the function
SQLFetch() to retrieve data. But php always uses SQLExtendedFetch()
that it fails.
Any idea how i can make php to use SQLFetch() instead of
SQLExtendedFetch() ???
Best Regards
Christos
------------------------------------------------------------------------
[2002-11-18 05:19:16] [EMAIL PROTECTED]
Could you please also tell me which compiler you used on Sun Solaris to
compile php?
The Sun c compiler ? or Gnu ? and which version
Regards
Christos
------------------------------------------------------------------------
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/20203
--
Edit this bug report at http://bugs.php.net/?id=20203&edit=1
