Re: mysql_affected_rows() function

From: Date: Tue, 06 Jan 2004 21:36:19 +0000
Subject: Re: mysql_affected_rows() function
References: 1 2  Groups: php.general 
Request: Send a blank email to php-general+get-173912@lists.php.net to get a copy of this message
Hello, I use PHP v. 4.3.3 and MySQL v 4.1.0a and I have the same experience as Tyler. Also when performing INSERT and UPDATE commands. And I also don't know why. Mike "Cpt John W. Holmes" <holmes072000@charter.net> píse v diskusním príspevku news:018901c3d49a$18024580$a629089b@tbhhccdr... > From: "Tyler Longren" <tyler@jdhost.com> > > > I don't think mysql_affected_rows() is working like it should for me. > > In the manual for mysql_affected_rows() it has this (Example 1): > > > > /* this should return the correct numbers of deleted records */ > > mysql_query("DELETE FROM mytable WHERE id < 10"); > > printf("Records deleted: %d\n", mysql_affected_rows()); > > > > However, when I do this: > > $delete_assignment = mysql_query("DELETE FROM consultingprojectassign > > WHERE workerid='$assigned[$i]'"); > > printf("Records deleted: %d\n", mysql_affected_rows()); > > > > It always says "Records deleted: 0". Even though the record was, > > indeed, deleted. I have an if statement also that says if > > mysql_affected_rows() < "1", then print an error message. Well, since > > it always returns 0, no matter what, the error is always shown, even > > when the record is deleted. > > I can't see a reason why that wouldn't work. Is that your exact code, i.e. > you're not doing anything else between the mysql_query() call and the > mysql_affected_rows() call? What versions of PHP/MySQL are you using? > > ---John Holmes...

« previous php.general (#173912) next »