| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Josh Kupershmidt <schmiddy(at)gmail(dot)com>, "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Pulling data from a constraint def |
| Date: | 2010-05-14 00:08:31 |
| Message-ID: | 10470.1273795711@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
David Fetter <david(at)fetter(dot)org> writes:
> On Thu, May 13, 2010 at 12:33:08AM -0400, Tom Lane wrote:
>> I'm surprised no one has yet suggested an ENUM type.
> I didn't suggest it because I didn't know about it, but because I've
> found ENUM to be a trap for the unwary.
> Very seldom are people absolutely certain that they'll have one
> particular list of things forever. The list may grow or shrink, or
> the order may change, and in those cases where the list changes
> somehow, ENUM causes more problems than it solves.
Well, the inability to change the list of values is certainly an
unpleasant limitation, but is it so fatal that we should hide the
feature from people who could possibly use it? I think not.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2010-05-14 00:14:36 | Re: Pulling data from a constraint def |
| Previous Message | David Fetter | 2010-05-13 23:42:31 | Re: Pulling data from a constraint def |