From: Tom Lane <tgl@sss.pgh.pa.us>
To: ldm@apartia.ch
Cc: pgsql-sql@postgresql.org
Subject: Re: protecting a field after creation
Date: Sun, 20 Aug 2000 13:31:24 -0400
Message-ID: <10467.966792684@sss.pgh.pa.us> (raw)
In-Reply-To: <20000820182933.A2917@styx>
References: <20000820182933.A2917@styx>
Louis-David Mitterrand <cunctator@apartia.ch> writes:
> Is there a way (outside of RULEs and TRIGGERs) to make a field
> read-only once it is INSERTed or assigned its default value? I'm
> thinking, for example, of the "created" column that I add to most
> tables, holding the row's creation timestamp.
An on-update trigger seems like a very simple solution here.
You could either copy the old value into the new, or raise an
error if they are different, depending on what you want.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, ldm@apartia.ch
Subject: Re: protecting a field after creation
In-Reply-To: <10467.966792684@sss.pgh.pa.us>
References: <20000820182933.A2917@styx> <10467.966792684@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox