PHP 4.0 Bug #4131 Updated: ODBC fetch_into/result_all access violation

ID: 4131 Updated by: kara Reported By: jean-pierre.parent@bpe.net Old-Status: Assigned Status: Closed Bug Type: ODBC related Assigned To: kara Comments: There hasn't been any feedback, so closing Previous Comments: --------------------------------------------------------------------------- [2000-07-25 22:21:07] zak@php.net Has there been any progress on this bug? --------------------------------------------------------------------------- [2000-04-17 05:56:57] kara@cvs.php.net Could you please try the following to nail down the problem: 1. Does odbc_result work with your MAX() statement? 2. Does odbc_result_all()/odbc_fetch_into() work with SQL statements that return more than 1 Row? Please turn on ODBC tracing for these tests. --------------------------------------------------------------------------- [2000-04-13 21:11:07] jean-pierre.parent@bpe.net Oracle's newest ODBC drivers can make MAX() work since the ODBCTEST program work and I just found that the drivers are level 3 ODBC compliant. Might help? I'd like to hack a patch but I never did that on any program. I also did a backtrace of the calls received by the Oracle 8i database and I can tell that the select was executed and that it returned something succesfully. So I believe that PHP might have a bug. I'll try to get more info... --------------------------------------------------------------------------- [2000-04-13 10:37:57] jean-pierre.parent@bpe.net Sorry I forgot to say that I use SP6 with my NT Server. --------------------------------------------------------------------------- [2000-04-13 10:33:04] jean-pierre.parent@bpe.net Update: both odbc_fetch_into() and odbc_result_all() functions crash odbc_exec() seems to work fine and returns a resource id but this id doesn't seem to be valid. --------------------------------------------------------------------------- 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=4131&edit=2