| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: add label to enum syntax |
| Date: | 2010-10-27 16:19:51 |
| Message-ID: | 9CDD4B10-85A0-4A41-851E-572D5D91B0D6@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Oct 27, 2010, at 7:18 AM, Andrew Dunstan wrote:
> The reason I chose LABEL was that it's consistent with what we have used elsewhere, both in the docs and the catalog. But I'm not strongly wedded to it. If it's a choice between ELEMENT and VALUE, I too prefer VALUE at it seems likelier to convey the sense of what we're doing to a naive user.
FWIW, MySQL seems to call them values:
> An ENUM is a string object with a value chosen from a list of permitted values that are enumerated explicitly in the column specification at table creation time.
-- http://dev.mysql.com/doc/refman/5.0/en/enum.html
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2010-10-27 16:24:41 | Re: Bikeshedding on enum vocabulary |
| Previous Message | Heikki Linnakangas | 2010-10-27 15:41:00 | Re: plan time of MASSIVE partitioning ... |