Skip site navigation (1) Skip section navigation (2)

Re: add label to enum syntax

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 (view raw or flat)
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

In response to

pgsql-hackers by date

Next:From: David E. WheelerDate: 2010-10-27 16:24:41
Subject: Re: Bikeshedding on enum vocabulary
Previous:From: Heikki LinnakangasDate: 2010-10-27 15:41:00
Subject: Re: plan time of MASSIVE partitioning ...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group