Bug #39792 | Need automatic CURRENT_TIMESTAMP capability in separate TIMESTAMP fields | ||
---|---|---|---|
Submitted: | 1 Oct 2008 21:37 | ||
Reporter: | Kevin Benton (Candidate Quality Contributor) | Email Updates: | |
Status: | Open | Impact on me: | |
Category: | MySQL Server: General | Severity: | S4 (Feature request) |
Version: | 4.1 thru 6.0 | OS: | Any |
Assigned to: | Geir Høydalsvik | CPU Architecture: | Any |
Tags: | qc |
[1 Oct 2008 21:37]
Kevin Benton
[28 Jul 2009 23:47]
Dimitriy A
Are there any plans to add this capability? The current workarounds of using triggers or stored procedures are not elegant. Some workarounds are posted in the comments section at http://dev.mysql.com/doc/refman/5.0/en/timestamp.html. Quoting part of the comment: "...all of these solutions require that the code doing the insert explicitly set a value for the created / inserted timestamp column - whether it is NULL or CURRENT_TIMESTAMP - there doesn't seem to be a way for MySQL to handle this implicitly." Seems this would require minimal coding.