| From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
| Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: extensible enums |
| Date: | 2010-08-23 17:53:05 |
| Message-ID: | 65021.203.166.48.226.1282585985.squirrel@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, August 23, 2010 11:49 am, Alvaro Herrera wrote:
> Excerpts from Andrew Dunstan's message of lun ago 23 05:35:09 -0400 2010:
>
>> To add a label at the end of the list, do:
>>
>> ALTER TYPE myenum ADD 'newlabel';
>>
>> To add a label somewhere else, do:
>>
>> ALTER TYPE myenum ADD 'newlabel' BEFORE 'existinglabel';
>>
>> or
>>
>> ALTER TYPE myenum ADD 'newlabel' AFTER 'existinglabel';
>
> What do you need AFTER for? Seems to me that BEFORE should be enough.
> (You already have the unadorned syntax for adding an item after the last
> one, which is the corner case that BEFORE alone doesn't cover).
>
You're right. Strictly speaking we don't need it. But it doesn't hurt much
to provide it for a degree of symmetry.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-23 17:54:40 | Re: WIP: extensible enums |
| Previous Message | Andrew Dunstan | 2010-08-23 17:42:29 | Re: WIP: extensible enums |