List:General Discussion« Previous MessageNext Message »
From:Paul DuBois Date:July 9 1999 8:45pm
Subject:Re: Problem with mutiple columns of type TIMESTAMP
View as plain text  
At 4:33 PM -0400 7/9/99, Daniel Koch wrote:
>Paul DuBois wrote:
>
>> If you want to maintain both a time-created value and a last-modified
>> value, do so as follows:
>>
>> * Use one TIMESTAMP for the time-modified value, and a second TIMESTAMP
>>    for the time-created value.
>>
>> * Make sure the time-modified column is the first TIMESTAMP, so that
>>    it's set when the record is created or changed.
>>
>> * Make the time-created column the second TIMESTAMP, and initialize it
>>    to NOW() when you create new records. That way its value will reflect
>>    the record creation time and will not change after that.
>>
>
>Or just use DATETIME for the creation-time column.


Yep.

-- 
Paul DuBois, paul@stripped
Northern League Chronicles: http://www.snake.net/nl/
Thread
Problem with mutiple columns of type TIMESTAMPDenny Chambers9 Jul
  • Re: Problem with mutiple columns of type TIMESTAMPBenjamin Pflugmann9 Jul
  • Re: Problem with mutiple columns of type TIMESTAMPPaul DuBois9 Jul
  • Re: Problem with mutiple columns of type TIMESTAMPDaniel Koch10 Jul
    • Re: Problem with mutiple columns of type TIMESTAMPPaul DuBois10 Jul
  • Re: Problem with mutiple columns of type TIMESTAMPFred Read10 Jul
    • Re: Problem with mutiple columns of type TIMESTAMPLuke10 Jul
RE: Problem with mutiple columns of type TIMESTAMPDarren L Sweeney9 Jul
  • Re: Problem with mutiple columns of type TIMESTAMPBenjamin Pflugmann9 Jul