From: | Andreas Kretschmer <akretschmer(at)spamfence(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Dynamic update of a date field |
Date: | 2012-02-16 14:27:39 |
Message-ID: | 20120216142739.GA31502@tux |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Musial, Jan (GIUB) <jan(dot)musial(at)giub(dot)unibe(dot)ch> wrote:
> Dear all,
>
> I have a question concerning default value/trigger function which
> supposed to update/fill field called time_stamp whenever a row is
> inserted. Let say that we have a table: CREATE TABLE dummy (year
you can use 'default now()' or an insert-trigger
> smallint,month smallint,day smallint,time_stamp date); I would like to
That's silly, use one (and only one) field, timestamp (or timestamptz)
Don't use never ever multiple columns for the same information!
Andreas
--
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect. (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly." (unknown)
Kaufbach, Saxony, Germany, Europe. N 51.05082°, E 13.56889°
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2012-02-16 14:44:14 | Re: [GENERA]: Postgresql-9.1.1 synchronous replication issue |
Previous Message | Stefan Keller | 2012-02-16 14:17:16 | Re: [postgis-users] ST_AsJpeg |