Re: forcing a literal value in a column - Mailing list pgsql-general

From Karsten Hilbert
Subject Re: forcing a literal value in a column
Date
Msg-id 20030513164316.W564@hermes.hilbert.loc
Whole thread Raw
In response to Re: forcing a literal value in a column  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
List pgsql-general
> I'm guessing you mean that you want the two columns to always be the
> user/time of the row's last modification, not always the current user and
> current time (of who/when a select is done).
Yes. I was imprecise.

> Assuming you want an automatically modified field, probably not.  As you
> noted, defaults aren't automatically propogated to columns on update.
> Triggers are probably the best way to do it.
Thanks. I've been implementing the triggers already. Seems to
work as expected.

Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346


pgsql-general by date:

Previous
From: Karsten Hilbert
Date:
Subject: Re: forcing a literal value in a column
Next
From: Bruno Wolff III
Date:
Subject: Re: Creating functions and triggers