| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Daniel Koch | Date: | July 9 1999 8:33pm |
| Subject: | Re: Problem with mutiple columns of type TIMESTAMP | ||
| View as plain text | |||
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. -- Dan Koch Webmaster American City Business Journals http://www.amcity.com/
| Thread | ||
|---|---|---|
| • Problem with mutiple columns of type TIMESTAMP | Denny Chambers | 9 Jul |
| • Re: Problem with mutiple columns of type TIMESTAMP | Benjamin Pflugmann | 9 Jul |
| • Re: Problem with mutiple columns of type TIMESTAMP | Paul DuBois | 9 Jul |
| • Re: Problem with mutiple columns of type TIMESTAMP | Daniel Koch | 10 Jul |
| • Re: Problem with mutiple columns of type TIMESTAMP | Paul DuBois | 10 Jul |
| • Re: Problem with mutiple columns of type TIMESTAMP | Fred Read | 10 Jul |
| • Re: Problem with mutiple columns of type TIMESTAMP | Luke | 10 Jul |
| • RE: Problem with mutiple columns of type TIMESTAMP | Darren L Sweeney | 9 Jul |
| • Re: Problem with mutiple columns of type TIMESTAMP | Benjamin Pflugmann | 9 Jul |
