| From: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How to modify ENUM datatypes? |
| Date: | 2008-04-24 19:01:14 |
| Message-ID: | 4810D8FA.3040706@wildenhain.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Merlin Moncure wrote:
> On Thu, Apr 24, 2008 at 12:22 PM, Andrew Sullivan <ajs(at)crankycanuck(dot)ca> wrote:
>> The first time I encountered them, I thought enums were a filthy,
>> ill-conceived answer to a problem that didn't exist, implemented by people
>> who didn't understand relational databases. With considerably more
>> experience under my belt than then, I say now that my original estimation
>> was too kind.
>
> I think you're being a little too hard on enums here. I was actually
> in the anti-enum camp until it was demonstrated to me (and in my own
> testing) that using enum for natural ordering vs. fielding the
> ordering of the type out to a join is can be a huge win in such cases
> where it is important. Relational theory is all well and good, but in
> practical terms things like record size, index size, and query
> performance are important.
Uhm. Sorry what? Can you demonstrate this particular use?
When I first saw discussion about enumns I kinda hoped they
will be implemented as kind of macro to really map to a table.
But here you go. I'm still looking for a good example to
demonstrate the usefullness of enums (same for arrays for that
matter)
Cheers
Tino
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Howard Cole | 2008-04-24 19:10:54 | Multiple Database Strategy |
| Previous Message | Alban Hertroys | 2008-04-24 18:31:49 | Re: I think this is a BUG? |