Re: add label to enum syntax
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, "David E. Wheeler" <david@kineticode.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-10-25T20:14:18Z
Lists: pgsql-hackers
On 10/25/2010 04:03 PM, Pavel Stehule wrote: > 2010/10/25 Andrew Dunstan<andrew@dunslane.net>: >> >> On 10/25/2010 02:51 PM, Robert Haas wrote: >>> >>> Personally, I prefer LABEL. But I could live with VALUE. >> That's roughly my position. It would be consistent with the name we use in >> the catalogs, as well as what's in the docs. I don't think it's as opaque as >> Tom seems to suggest. An enum is pretty much an ordered set of labels. But I >> could certainly live with VALUE if that's the consensus. > I agree with you. There are some better keywords than VALUE - maybe > ELEMENT or just LABEL. I understand if there must be a reserved > keyword - but if not I prefer LABEL too. > LABEL is already an unreserved keyword, and I'm pretty sure that's all we'll need. cheers andrew