Received: from styx.apartia.int (postfix@r34m39.cybercable.tm.fr [195.132.34.39]) by hub.org (8.10.1/8.10.1) with ESMTP id e7KGTLm42056 for ; Sun, 20 Aug 2000 12:29:21 -0400 (EDT) Received: by styx.apartia.int (Postfix, from userid 1000) id DF255571A; Sun, 20 Aug 2000 18:29:33 +0200 (CEST) Date: Sun, 20 Aug 2000 18:29:33 +0200 From: Louis-David Mitterrand To: pgsql-sql@postgresql.org Subject: protecting a field after creation Message-ID: <20000820182933.A2917@styx> Reply-To: ldm@apartia.ch Mail-Followup-To: pgsql-sql@postgresql.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Archive-Number: 200008/188 Hello, 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. Thanks in advance, -- Louis-David Mitterrand - ldm@apartia.org - http://www.apartia.org Murphy's Guide to Science: If it's green or squirms, it's biology. If it stinks, it's chemistry. If it doesn't work, it's physics.