Bug #82166 | update the other field which isn't the specified field. | ||
---|---|---|---|
Submitted: | 8 Jul 2016 10:27 | Modified: | 8 Jul 2016 11:10 |
Reporter: | Maxwell Lee | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: DML | Severity: | S2 (Serious) |
Version: | 5.6.30 | OS: | CentOS (Linux 2.6.32-431.11.5.el6.ucloud.x86_64 #1 SMP) |
Assigned to: | CPU Architecture: | Any |
[8 Jul 2016 10:27]
Maxwell Lee
[8 Jul 2016 11:10]
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/refman/5.6/en/timestamp-initialization.html and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php I see " `start_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP," which expected to behave as documented i.e "An auto-updated column is automatically updated to the current timestamp when the value of any other column in the row is changed from its current value"