#32251 [Opn->Csd]: mysql_affected_rows: returns correct # of rows when DELETE with no WHERE

ID: 32251 Updated by: vrana@php.net Reported By: tpavlakos at yahoo dot gr -Status: Open +Status: Closed Bug Type: Documentation problem Operating System: Win2000 SP4 PHP Version: 4.3.9 New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. "... function will return zero with MySQL versions prior to 4.1.2." Previous Comments: ------------------------------------------------------------------------ [2005-03-09 12:50:01] tpavlakos at yahoo dot gr Description: ------------ From the 'mysql_affected_rows' doc page: " If the last query was a DELETE query with no WHERE clause, all of the records will have been deleted from the table but this function will return zero." (At least with MySQL 4.1.10) This doesn't seem to be correct. The correct number of rows deleted is returned. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=32251&edit=1