| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| 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:23:26 |
| Message-ID: | 20051028202326.GU13187@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-10-28 20:29:13 | Re: TRAP: FailedAssertion("!((itemid)->lp_flags & 0x01)", |
| Previous Message | Jim C. Nasby | 2005-10-28 20:21:59 | Re: enums |