X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4C4C0DBE77 for ; Tue, 22 Nov 2005 19:28:53 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 12204-09 for ; Tue, 22 Nov 2005 23:28:55 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by svr1.postgresql.org (Postfix) with ESMTP id A7B5BDBE6F for ; Tue, 22 Nov 2005 19:28:50 -0400 (AST) Received: from [192.168.1.12] ([141.156.211.154]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IQD00LK6QK4YZV5@vms042.mailsrvcs.net> for pgsql-admin@postgresql.org; Tue, 22 Nov 2005 17:28:53 -0600 (CST) Date: Tue, 22 Nov 2005 18:28:55 -0500 From: Ferindo Middleton Jr Subject: freezing a particular field in a table To: pgsql-admin@postgresql.org Reply-to: fmiddleton@verizon.net Message-id: <4383A9B7.7060008@verizon.net> Organization: Sleek Collar MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit User-Agent: Thunderbird 1.4.1 (Windows/20051006) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=1.279 required=5 tests=[AWL=-0.640, DNS_FROM_RFC_ABUSE=0.479, DNS_FROM_RFC_POST=1.44] X-Spam-Score: 1.279 X-Spam-Level: * X-Archive-Number: 200511/302 X-Sequence-Number: 19675 Is there a way where you can implement a situation in a postgres table where a particular field cannot be changed when saved initially. I have table and there's one particular integer field that should never be changed in any record inserted... but I might need to allow the entire record to be deleted... I was just wondering if there's a way to implement something like this on a field (but not the entire row) at the database level? Ferindo Middleton