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

From: Date: Fri, 25 Mar 2005 15:07:57 +0000
Subject: #32454 [Opn->Bgs]: ibase_affected_rows always returns 0
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-75861@lists.php.net to get a copy of this message
ID: 32454 Updated by: abies@php.net Reported By: m dot muncke at computer1020 dot at -Status: Open +Status: Bogus Bug Type: InterBase related Operating System: Suse 9 PHP Version: 5.0.3 New Comment: 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. Previous Comments: ------------------------------------------------------------------------ [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

« previous php.bugs (#75861) next »