| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | Michael Fuhr <mike(at)fuhr(dot)org>, ted(at)php(dot)net, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: enums |
| Date: | 2005-10-28 20:31:36 |
| Message-ID: | 43628AA8.4030601@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim C. Nasby wrote:
>On Fri, Oct 28, 2005 at 04:12:01PM -0400, Andrew Dunstan wrote:
>
>
>>Well, with enumkit you can't, because the values are hardwired in the
>>.so file. With a builtin facility you would be able to, because the
>>values would live in the catalog. However, hacking the catalog is not
>>something I would encourage - what you are suggesting basically breaks
>>the abstraction. But sure, it would be possible. I would not provide an
>>SQL level facility to do it, though. My approved way to do it would be
>>like the example I gave earlier.
>>
>>
>
>Why not allow renaming though? It seems like a logical feature to have,
>and an easy one to add. What am I missing?
>
>
That it is not changing a name, but a value. It's roughly the equivalent
of inserting a new digit between 3 and 4. Your "feature" breaks the
abstraction I am trying to implement.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2005-10-28 20:36:26 | Re: enums |
| Previous Message | Jim C. Nasby | 2005-10-28 20:29:13 | Re: TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", |