| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, David E(dot) Wheeler <david(at)kineticode(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 14:57:54 |
| Message-ID: | 1288191290-sup-3346@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Andrew Dunstan's message of mié oct 27 11:18:44 -0300 2010:
> 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.
Wow, this must be the most difficult smallest thing I have ever seen
discussed in pg-hackers. It doesn't seem like there are enough votes
in any particular direction. Now *this* is proper bikeshedding.
Should we ask more openly in another thread, with a different, more
catchy subject?
And I just realized that my patch lacks psql tab completion support.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-10-27 15:06:17 | Re: xlog.c: WALInsertLock vs. WALWriteLock |
| Previous Message | Andrew Dunstan | 2010-10-27 14:49:53 | Re: add label to enum syntax |