Re: s/LABEL/VALUE/ for ENUMs

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: s/LABEL/VALUE/ for ENUMs
Date: 2010-11-23 19:01:33
Message-ID: BDDBDEA9-DAE3-4429-8013-4D1E741F164B@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Nov 22, 2010, at 6:03 PM, Josh Berkus wrote:

> ... "original patch". Sorry. Let's not fiddle with the names.

To be clear, as things stand now, the new command is:

ALTER TYPE name ADD VALUE new_enum_value [ { BEFORE | AFTER } existing_enum_value ]

So while the term in the SQL statement is "VALUE," it's called a "label" in the documentation. I think that's confusing. Does anyone else?

Best

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2010-11-23 19:27:42 Re: multibyte-character aware support for function "downcase_truncate_identifier()"
Previous Message Robert Haas 2010-11-23 18:50:19 Re: final patch - plpgsql: for-in-array