On Fri, Nov 12, 2010 at 1:55 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> On 11/12/2010 01:40 PM, Bruce Momjian wrote:
>>> FYI, I marked the TODO item for adding enums as completed. The TODO
>>> item used to also mention renaming or removing enums, but I have seen
>>> few requests for that so I removed that suggestion. We can always
>>> re-add it if there is demand.
>
>> Renaming an item would not be terribly hard. Removing one is that nasty
>> case. There are all sorts of places the old value could be referred to:
>> table data, view definitions, check constraints, functions etc.
>
> Well, you can rename an item today if you don't mind doing a direct
> UPDATE on pg_enum. I think that's probably sufficient if the demand
> only amounts to one or two requests a year. I'd say leave it off the
> TODO list till we see if there's more demand than that.
I'd say put it on and mark it with an [E]. We could use some more
[E]asy items for that list.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
