ID: 28871 Updated by: [EMAIL PROTECTED] Reported By: nav at nc dot ru -Status: Closed +Status: Bogus Bug Type: MySQL related Operating System: Windows XP PHP Version: 4.3.6 New Comment:
Not a bug -> bogus. Previous Comments: ------------------------------------------------------------------------ [2004-07-07 14:02:16] nav at nc dot ru I suppose now, that somewhere the code works twice - I hardly believe it should be a bug in both functions. I will close the topic for now. ------------------------------------------------------------------------ [2004-07-07 13:48:51] nav at nc dot ru Btw, now I've discovered, that mysql_num_rows after SELECT query doesn't work either! Or, to be more precise, it works the same wrong way as mysql_affected_rows. That's getting interesting... ------------------------------------------------------------------------ [2004-06-30 08:41:31] [EMAIL PROTECTED] Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.php.net/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to "Open". Thank you for your interest in PHP. Please provide a complete and reproducable testcase/script (including table definition and plain sql statements). ------------------------------------------------------------------------ [2004-06-22 12:07:52] nav at nc dot ru No, I carefully checked the record before and after UPDATE. It WAS changed. However, mysql_affected_rows returned 0. ------------------------------------------------------------------------ [2004-06-22 00:47:51] [EMAIL PROTECTED] Maybe the data is unchanged, meaning that it already was what you were trying to change it to. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/28871 -- Edit this bug report at http://bugs.php.net/?id=28871&edit=1
