If you want to see the actual date and time the data was updated, then
yes, you will need to add a trigger to handle this. If you don't like
the idea of a trigger, an alternative would be to code all of your
update code in parameterized stored procedures where the stored
procedure adds the datetime value as part of the update. You then need
to disallow direct data entry into the table, and code your
application to use only the update stored procedure.
--Mary
On 1 Feb 2005 12:47:55 -0800, "Nathan Waddington"
<(E-Mail Removed)> wrote:
>Hello Mary,
>
>Thanks for the info, I want to display the data as I thought it was
>actually a timestamp. I want a timestamp, I'd like to know when the
>record was last updated. It seems like I need to build some triggers
>in order to set a datetime on insert and update to achieve what I want
>then. Although the actual use of Timestamp is intriguing and I will
>have to look into it further.
>
>Thanks again,
>Nathan.
|