Hi Scott,
> Do you mean when the table was modified
> (i.e. alter table add column) or when the
> data in the table was changed?
I mean the latter, the data change.
> If it's when the table was changed, the
> easiest way is to store that in the comment
> for the table whenever you alter it.
Great idea! That's my ticket to solution.
Many thanks. I appreciate it.
Regards,
Tena Sakai
tsakai@gallo.ucsf.edu
-----Original Message-----
From: Scott Marlowe [mailto:scott.marlowe@gmail.com]
Sent: Tue 10/20/2009 1:44 PM
To: Tena Sakai
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] can I get a bit more attribute out of \dt directive?
On Tue, Oct 20, 2009 at 2:42 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:
> Hi Scott,
>
> Thank you for your reply.
>
>> That information is not stored by the db really,
>> so there's no way to get it.
>
> I think then I would build another column for
> timestamp. But in object-oriented lingo, this
> would be a class field, rather than instance
> field, and I don't want to timestamp every row
> of each table. The timestamp is strictly to
> tell when it was last modified.
>
> Is there any good way to do this?
Do you mean when the table was modified (i.e. alter table add column)
or when the data in the table was changed? If it's when the table was
changed, the easiest way is to store that in the comment for the table
whenever you alter it. Otherwise, you'll want a trigger or something
to store the latest update time in the latest row updated. There's
probably other ways too, but would involve a separate table to store
such things.