Re: add label to enum syntax

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: David E(dot) Wheeler <david(at)kineticode(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 00:45:25
Message-ID: 1288140208-sup-5735@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Dean Rasheed's message of mar oct 26 15:46:56 -0300 2010:
> On 26 October 2010 17:04, David E. Wheeler <david(at)kineticode(dot)com> wrote:
> > On Oct 26, 2010, at 7:15 AM, Robert Haas wrote:
> >
> >>> Notwithstanding the above, I don't think ELEMENT would be a very bad choice.
> >>
> >> I still think we should just go for LABEL and be done with it.  But
> >> y'all can ignore me if you want...
> >
> > +1
>
> Well ELEMENT is a reserved keyword in SQL:2008, to support multisets,
> so if we ever supported that feature...

Hah!

Well, here's a patch for LABEL in any case. If we're going to have to
reserve ELEMENT in the future then there doesn't seem to be much point
in not choosing that one though. Should we take a poll?

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Attachment Content-Type Size
0001-Change-syntax-to-add-a-new-enum-value-to-ALTER-TYPE-.patch application/octet-stream 12.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-10-27 01:06:56 Re: O_DSYNC broken on MacOS X?
Previous Message Robert Haas 2010-10-26 23:36:08 Re: psql: Don't close stdin, don't leak file descriptor with ON_ERROR_STOP