#32454 [Bgs->Opn]: ibase_affected_rows always returns 0

ID: 32454 Updated by: derick@php.net Reported By: m dot muncke at computer1020 dot at -Status: Bogus +Status: Open -Bug Type: InterBase related +Bug Type: Documentation problem Operating System: Suse 9 PHP Version: 5.0.3 New Comment: Marking as doc problem then. Previous Comments: ------------------------------------------------------------------------ [2005-03-25 18:10:54] m dot muncke at computer1020 dot at ok, this was not documented. Thank you for fast reply. ------------------------------------------------------------------------ [2005-03-25 16:07:56] abies@php.net ibase_affected_rows() returns the number of rows that were modified by the previous INSERT, UPDATE or DELETE. It does *not* return the number of rows available for fetching from a SELECT query. ------------------------------------------------------------------------ [2005-03-25 14:44:53] m dot muncke at computer1020 dot at Description: ------------ ibase_affected_rows() always returns 0 even if the select count(*) does not. I always recieve 0 rows IBConsole : select count(*) from Table ; -> returns 12 rows Reproduce code: --------------- $db = ibase_pconnect('localhost:/data/database/foo.fdb','SYSDBA','masterkey'); $query = "select * from Table"; $ret = ibase_query ($query); $zu = ibase_affected_rows ( $db) ; if ($zu == 0 ) echo ("query returns 0 rows"); else echo ("query returns at least 1 row "); Expected result: ---------------- Expected result : ibase_affected_rows should return number "12" as a select in isql or IBConsole does return 12 rows; Actual result: -------------- Actual result is always 0 ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=32454&edit=1