Easy enough to rectify....
ALTER TABLE `tbl_xyz` ADD COLUMN `updated_on` TIMESTAMP NOT NULL DEFAULT
CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP AFTER `prod_id`;
Personally I put a 'created_on' and an 'updated_on' column for mostly every
table I create.
3000 rows is nothing. A mere blink of an eye to mySQL. The database I'm
using is almost a Billion (yes, with a B, and I mean a good ol' USA 10^9
Billion, not that goofy long scale 10^12 "Billion"*) rows and 90GB. So
don't worry about it. Plus it's stored internally as an integer (timestamp)
> -----Original Message-----
> From: MadTh [mailto:madan.feedback@stripped]
> Sent: Monday, June 14, 2010 2:23 PM
> To: mysql@stripped
> Subject: Re: list rows with no recent updates
> Thank you all for your prompt response. Unfortunately
> timestamp file isn;t
> there, so I will find some other way to do it.
> Seems timestamp is a valuable field ( unless you want to
> save resource on
> generating timestamps on a very busy table).