ID:               16827
 Updated by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
-Status:           Open
+Status:           Bogus
 Bug Type:         ODBC related
 Operating System: Linux, Debian 2.2
 PHP Version:      4.2.0
 New Comment:

Thank you for taking the time to report a problem with PHP.
Unfortunately your version of PHP is too old -- the problem
might already be fixed. Please download a new PHP
version from http://www.php.net/downloads.php

If you are able to reproduce the bug with one of the latest
versions of PHP, please change the PHP version on this bug report
to the version you tested and change the status back to "Open".
Again, thank you for your continued support of PHP.




Previous Comments:
------------------------------------------------------------------------

[2002-04-25 13:57:58] [EMAIL PROTECTED]

I have noticed that all the DB2 (v7.1) accessing code (via the unified
ODBC functions) fails to be able to gather results under PHP4.2.0.

PHP is not crashing, and script execution continues past the points of
failure, and no error messages are displayed or logged. It appears that
there is just no data coming back from the odbc_do() function, although
the return code of odbc_fetch_into() is greather than zero.

PHP configure line: 

--with-apache=../apache --enable-trans-sid --with-zlib
--with-mysql=/usr/local/ --with-ibm-db2=/usr/IBMdb2/V7.1/ --with-ldap
--with-mcrypt --with-imap --with-gd=/usr/ --with-png-dir=/usr/
--with-jpeg-dir=/usr/

Yes, I know there's a lot of stuff compiled in, but I need and use it
all :)

I have done a clean build every time for my setup, and the results are
the same with PHP 4.2.0.

PHP 4.1.2 does NOT exhibit this problem, using the same compile time
options as above - and running on the exact same pages on the same
machine, even a recompile with PHP4.1.2 yields a fully working system.

Thanks,

Derek


------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=16827&edit=1

Reply via email to