Re: Datestamps

From: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
To: Bruno Wolff III <bruno(at)wolff(dot)to>, Bryan Irvine <bryan(dot)irvine(at)kingcountyjournal(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Datestamps
Date: 2004-01-09 21:47:17
Message-ID: 200401091347.17487.scrawford@pinpointresearch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Friday 09 January 2004 12:52 pm, Bruno Wolff III wrote:
> On Fri, Jan 09, 2004 at 12:25:45 -0800,
>
> Bryan Irvine <bryan(dot)irvine(at)kingcountyjournal(dot)com> wrote:
> > On Fri, 2004-01-09 at 12:25, Bruno Wolff III wrote:
> > > On Fri, Jan 09, 2004 at 11:45:17 -0800,
> > >
> > > Bryan Irvine <bryan(dot)irvine(at)kingcountyjournal(dot)com> wrote:
> > > > I am trying to figure out what day some things were entered
> > > > into the DB. Is there a way to do that?
> > >
> > > Rows do not have timestamps associated with them. You might be
> > > able to make some guesses using your logfile. If this is
> > > something you want for the future you can add a timestamp field
> > > to your table and use a trigger to keep it up to date.
> >
> > I do I do!
> >
> > What's the best way to create a field for tracking this?
> > Is this in the FAQ somewhere?
>
> I don't think there is an FAQ, but it has been discussed on the
> lists a few times. You probably want to use a before trigger to set
> the timestamp column to current_timestamp on inserts or updates.

Creating a timestamp on inserts (not updates) is easy:

create table foo (....., mytimestamp timestamptz not null default
now(), ...);

Cheers,
Steve

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message bartvde 2004-01-09 22:40:20 createdb
Previous Message Bruno Wolff III 2004-01-09 21:41:45 Re: psql error: could not connect to server