Bug #10181 Updated: odbc_result causes Unexpected network read error

ID: 10181 Updated by: kalowsky Reported By: f.schneider@de-bleek.demon.nl Old-Status: Open Status: Analyzed Bug Type: ODBC related Operating system: PHP Version: 4.0.4pl1 Assigned To: Comments: This sounds like a problem with the PHP cursor implementation, not OpenLink. Stephan Schadt and I have been working on a solution for this, and should hopefully have one ready in the near future. I'd like to say 4.0.7, but I'm not entirely sure. Previous Comments: --------------------------------------------------------------------------- [2001-07-04 07:01:50] f.schneider@de-bleek.demon.nl After some debugging of the ODBC module of php we have discoverd that the SQLExtendedFetch function of the OpenLink-progress driver is buggy. an query like: select * from table where field='text' will give us a valid result set, but an query like: select * from table where field='12345' will give us garbage: The driver does not set the 'result->values' arrays (but it returns SUCCESS and sets the correct number of collumns etc.) this results in variables which are pointing to some non-set, non-terminating strings ... The reason why python and the example programm work is that they don't use the SQLExtendedFetch function but SQLFetch. The fix for this problem is to undefine the HAVE_SQL_EXTENDED_FETCH definition in php_odbc.h at the iODBC definitions (if you use iODBC with openlink) or else at the OpenLink definitions. Maybe the php folks can give an extra option for openlink-progress ? so this can be solved more accurate? Thanks. --------------------------------------------------------------------------- [2001-06-21 11:20:57] kalowsky@php.net best way to debug is to build as a CGI and set a break in the function you think might be causing it. then run and step through the code. --------------------------------------------------------------------------- [2001-06-13 09:03:53] f.schneider@de-bleek.demon.nl Version 4.0.5 has exactly the same problem. Could this be a problem with type conversion? How should I debug? --------------------------------------------------------------------------- [2001-06-10 16:11:35] kalowsky@php.net you can look in the ext/odbc/php_odbc.c file for what might be causing this. the ext/odbc/php_odbc.h may also be of some help. also you might wish to try the 4.0.5 release of PHP, or possibly the 4.0.6RCs (4.0.5 was in RC for a LONG time). --------------------------------------------------------------------------- [2001-06-01 17:23:40] f.schneider@de-bleek.demon.nl Hitting the refresh button on the browser will return different results each time. The number of rows seems correct. It doesn't look like a problem with the drivers since they work fine with Python or the test programm included with the driver. Could this be a problem with type casting? Where should I look in the PHP source code? --------------------------------------------------------------------------- The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online. ATTENTION! Do NOT reply to this email! To reply, use the web interface found at http://bugs.php.net/?id=10181&edit=2