#19349 [Bgs->Opn]: odbc_longreadlen() does not work

ID: 19349 User updated by: truth@ichaos.com Reported By: truth@ichaos.com -Status: Bogus +Status: Open Bug Type: ODBC related Operating System: SuSE 8.0 PHP Version: 4.2.1 New Comment: I have a script that runs a select statement from a 10MB CLOB field (among others). I run the following : odbc_longreadlen($resultid, 3000000); Then I run: $document = odbc_result($resultid, 2); The problem is, $document ends up with 4096 bytes of data (the default, NOT 3000000). If I edit php.ini and set up odbc_lrl to 2000000 in there, then $document ends up with 2MBin it. It acts like the function odbc_longreadlen does not work at all. I don't know how much more information I can give other than odbc_longreadlen does not seem to do anything at all. Previous Comments: ------------------------------------------------------------------------ [2002-09-11 09:49:21] kalowsky@php.net Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.php.net/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to "Open". Thank you for your interest in PHP. ------------------------------------------------------------------------ [2002-09-10 20:33:11] truth@ichaos.com I am using PHP with ODBC (IBM DB2) support and since upgrading to 4.2.1 from 4.0.4pl1, my odbc_longreadlen() function no longer works. I have to set it in the configuration file now, as that is the only place that it works properly. In addition, when it's set above 2000000 in the config file, httpd starts taking 75% of the CPU (system, not user) and the data never gets to PHP. Am I hitting some type of limitation? How else do I get my 10MB CLOB out of DB2? ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=19349&edit=1