From: | "Jason Minion" <jason(dot)minion(at)sigler(dot)com> |
---|---|
To: | <fmiddleton(at)verizon(dot)net>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: freezing a particular field in a table |
Date: | 2005-11-22 23:38:31 |
Message-ID: | 0105A1BF505D304E9E5AF38B63E40E4E82E10C@EXCHANGE.siglercompanies.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Perhaps a BEFORE UPDATE trigger, setting NEW.do_not_change_me =
OLD.do_not_change_me?
Jason Minion
IT Developer
Sigler Printing & Publishing
413 Northwestern Ave
Ames, IA 50010
515-232-6997
jason(dot)minion(at)sigler(dot)com
-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Ferindo Middleton
Jr
Sent: Tuesday, November 22, 2005 5:29 PM
To: pgsql-admin(at)postgresql(dot)org
Subject: [ADMIN] freezing a particular field in a table
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
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly
From | Date | Subject | |
---|---|---|---|
Next Message | hubert depesz lubaczewski | 2005-11-23 09:28:01 | Re: freezing a particular field in a table |
Previous Message | Ferindo Middleton Jr | 2005-11-22 23:28:55 | freezing a particular field in a table |