php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Doc Bug #32251 mysql_affected_rows: returns correct # of rows when DELETE with no WHERE
Submitted: 2005-03-09 12:50 UTC Modified: 2005-03-15 13:57 UTC
From: tpavlakos at yahoo dot gr Assigned:
Status: Closed Package: Documentation problem
PHP Version: 4.3.9 OS: Win2000 SP4
Private report: No CVE-ID: None
View Developer Edit
 [2005-03-09 12:50 UTC] 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.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-03-15 13:57 UTC] vrana@php.net 
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."
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Sat Jul 26 19:00:03 2025 UTC