From: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Jeroen Vermeulen <jtv(at)xs4all(dot)nl>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: foreign key locks, 2nd attempt |
Date: | 2011-11-10 20:38:41 |
Message-ID: | CAFNqd5Ui+=3YcM=WWBsPDjy0Q0FFwy87q9BPrT2fcaJBS3s0cg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 10, 2011 at 3:29 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Christopher Browne <cbbrowne(at)gmail(dot)com> wrote:
>
>> There's value in having an "immutability" constraint on a column,
>> where, in effect, you're not allowed to modify the value of the
>> column, once assigned.
>
> +1 We would definitely use such a feature, should it become
> available.
Added to TODO list.
--
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-11-10 20:41:42 | Re: proposal: psql concise mode |
Previous Message | Kevin Grittner | 2011-11-10 20:29:44 | Re: foreign key locks, 2nd attempt |