#19528 [Opn->Fbk]: odbc_function_row() doesn't returned true if there is one row only

ID: 19528 Updated by: kalowsky@php.net Reported By: scott@abcoa.com -Status: Open +Status: Feedback Bug Type: ODBC related Operating System: AIX (UNIX) PHP Version: 4.2.2 New Comment: Creating a sql.log is typically defined in your odbc.ini file, per DSN. You may have to alter that to turn on logging. As per the specific lines, that depends upon your vendors specific implementation. Previous Comments: ------------------------------------------------------------------------ [2002-09-26 11:11:36] scott@abcoa.com Disregard my last comment, the bug workaround still work. I made the typo in the counter. So, that leave the original bug as unchanged. ------------------------------------------------------------------------ [2002-09-26 11:01:23] scott@abcoa.com To my dismay, I thought that including hte counter as the 2nd paramater to the odbc_fetch_row() function would fix this problem but it turned out that it doesn't. It turned out that it help a little bit but it is only an intermitted problem. ------------------------------------------------------------------------ [2002-09-26 10:57:50] scott@abcoa.com I have found no sql.log file on this webserver. Any comments or suggestion? ------------------------------------------------------------------------ [2002-09-26 10:47:30] kalowsky@php.net can you please make a sql log file and post the results of this? It would make debugging this a lot easier :) ------------------------------------------------------------------------ [2002-09-26 10:32:59] scott@abcoa.com I found one interesting observation when I write a short test script. It showed that if I use the odbc_fetch_row() only, it work fine. It showed that if I use the odbc_fetch_into() only, it work fine. It showed that if I use both the odbc_fetch_row() and odbc_fetch_into(), it showed a minor problem, that is not being able to display one row if there is only one row. But work fine when there's two rows or more. ------------------------------------------------------------------------ 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/19528 -- Edit this bug report at http://bugs.php.net/?id=19528&edit=1