Sometimes you can get fooled by the result. If nothing is changed on a update the result for this function will give 0, because nothing was affected. Although you might think so just because you are doing an "update". However, an update doesn't necessary mean an update :) Best regards, Peter Lauri www.dwsasia.com - company web site www.lauri.se - personal web site www.carbonfree.org.uk - become Carbon Free -----Original Message----- From: altendew [mailto:andrew@xxxxxxxxxxxxx] Sent: Thursday, February 15, 2007 6:06 PM To: php-general@xxxxxxxxxxxxx Subject: mysql_affected_rows inaccurate? Hi a long time ago I stopped using mysql_affected_rows because I believed it was giving me an inaccurate number. Now I was not very knowledged then so it could of been my own fault. Is this function safe and functional? Could it possibly give me the row result of a previous query I did and not the latest? -- View this message in context: http://www.nabble.com/mysql_affected_rows-inaccurate--tf3234567.html#a898812 3 Sent from the PHP - General mailing list archive at Nabble.com. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
