Re: enum bug

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Elein <elein(at)varlena(dot)com>, GENERAL <pgsql-general(at)postgresql(dot)org>
Subject: Re: enum bug
Date: 2016-03-14 16:07:48
Message-ID: 56E6E1D4.4090700@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 03/14/2016 09:02 AM, David G. Johnston wrote:

> ​The one nice thing about enums is that you get two concepts in one
> column - a human readable label and a system used ordering.
>
> i.e., "SELECT enum_value FROM tbl ORDER BY enum_value" actually
> ​
> ​gives you a meaningful order without having to carry around, or relink
> to, a lookup table to get an ordering column.
>
> ​Now, this is a bit overrated since you immediately lose that ability if
> you export to a Spreadsheet program, or otherwise lose the ordering
> nature during a convert-to-text operation.
>

I do not suggest that ENUMS are useless just that there are more
flexible and reasonable ways (as a whole) to do what ENUMS provide.

Sincerely,

JD

--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.

In response to

  • Re: enum bug at 2016-03-14 16:02:22 from David G. Johnston

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Melvin Davidson 2016-03-14 16:09:32 Re: enum bug
Previous Message David G. Johnston 2016-03-14 16:02:22 Re: enum bug