Bug #21762 | UPDATE setting a field to null when already set to null results in a changed row | ||
---|---|---|---|
Submitted: | 21 Aug 2006 19:08 | Modified: | 21 Aug 2006 22:36 |
Reporter: | Nicholas Costa | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0.20a | OS: | Linux (Ubuntu) |
Assigned to: | CPU Architecture: | Any |
[21 Aug 2006 19:08]
Nicholas Costa
[21 Aug 2006 22:36]
MySQL Verification Team
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Additional Info: The server behaves according the SQL Standard (NULL = UNKNOWN) then in any case an update is performed. Please see also: http://dev.mysql.com/doc/refman/5.0/en/problems-with-null.html