Bug #7023 | UPDATE queries change value of TIMESTAMP field even when not instructed to | ||
---|---|---|---|
Submitted: | 5 Dec 2004 18:19 | Modified: | 5 Dec 2004 21:41 |
Reporter: | Steve Opilo | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: MyISAM storage engine | Severity: | S3 (Non-critical) |
Version: | 4.0.21 | OS: | Windows (Windows 2000) |
Assigned to: | CPU Architecture: | Any |
[5 Dec 2004 18:19]
Steve Opilo
[5 Dec 2004 21:41]
Hartmut Holzgraefe
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.mysql.com/documentation/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Additional info: TIMESTAMP columns are meant to track the time of the last change applied to a column. If you do not want this automatic behaviour you should use DATETIME instead. See also http://dev.mysql.com/doc/mysql/en/TIMESTAMP_pre-4.1.html "The TIMESTAMP column type provides a type that you can use to automatically mark INSERT or UPDATE operations with the current date and time."