Bug #7438 [Com]: mysql_affected_rows not working

Edit report at https://bugs.php.net/bug.php?id=7438&edit=1 ID: 7438 Comment by: cbal at freemail dot hu Reported by: juancho at metallica dot com Summary: mysql_affected_rows not working Status: Closed Type: Bug Package: MySQL related Operating System: Mandrake 7.0 PHP Version: 4.0.3pl1 Block user comment: N Private report: N New Comment: see this: http://stackoverflow.com/questions/7303304/mysql-affected-rows-does-not-work-for-checking-if-row-exists this solves the problem Previous Comments: ------------------------------------------------------------------------ [2000-10-25 16:33:57] torben@php.net This is not a bug--mysql_affected_rows() takes as its argument a link identifier (i.e., what you get from mysql_pconnect()), and not a result identifier. Try passing $conn instead of $r and you should get what you want. Hope this helps. ------------------------------------------------------------------------ [2000-10-24 16:51:38] juancho at metallica dot com sorry, the correct query is "update mytable set x='y' where z='p' " ------------------------------------------------------------------------ [2000-10-24 16:46:43] juancho at metallica dot com ./configure' '--with-apache=../apache_1.3.14' '--enable-track-vars' '--enable-ftp' '--enable-trans-sid' '--disable-debug' '--enable-magic-quotes' <? $conn=mysql_ponnect("localhost","user","pass"); $r=mysql_db_query("mydb","update x='y' where z='p' ",$conn); $n=mysql_affected_rows($r); echo "n= $n"; ?> It prints "n= " and I get this warning: Warning: Supplied argument is not a valid MySQL-Link resource in /mnt/clientes/sancho/html/classes/manage_users.php on line 143 but the data in the database is beeing modified by the update query. It worked fine with 4.0.1pl2 php.ini: [MySQL] mysql.allow_persistent = On mysql.max_persistent = -1 mysql.max_links = -1 mysql.default_port = mysql.default_host = mysql.default_user = mysql.default_password = ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=7438&edit=1