| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Elein <elein(at)varlena(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | GENERAL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: enum bug |
| Date: | 2016-03-14 15:25:28 |
| Message-ID: | 56E6D7E8.4010003@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 03/11/2016 03:19 PM, Elein wrote:
> An unused (yet) enum type cannot display the enum ranges. An empty table
> containing that type cannot display enum ranges.
>
> The example selects were what I did to figure out that enum_ranges only
> worked on existing data. Sorry if they were confusing. But the way enum
> values are currently displayed is confusing.
>
> Enums are evil because of the difficulty working with them. They should
> be used for a fixed set of valid values. Otherwise use a lookup table.
"Otherwise use a lookup table."
That is the solution to this problem.
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-03-14 15:48:03 | Re: enum bug |
| Previous Message | David G. Johnston | 2016-03-14 15:22:38 | Re: Suppress decimal point like digits in to_char? |