Re: [HACKERS] Enticing interns to PostgreSQL

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Jeff Davis <jdavis-pgsql(at)empires(dot)org>
Cc: pgsql-advocacy(at)postgresql(dot)org, Chris Travers <chris(at)travelamericas(dot)com>, "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
Subject: Re: [HACKERS] Enticing interns to PostgreSQL
Date: 2005-07-27 18:05:22
Message-ID: 200507272005.23533.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-hackers

Jeff Davis wrote:
> I mostly agree, but I don't think we can dismiss enum completely.
> After all, boolean is pretty much enum(false,true), and nobody would
> advocate removing that type.

I think you can make the mathematical argument that enums are valid and
useful. I'm not going to do that here, but some thoughts: As you
point out, any scalar type is really just a set of conveniently chosen
symbols that are made interesting by functions and operators. In
traditional programming languages as well as in the MySQL case, "enums"
are just a short-hand way to define such a scalar type without any
interesting operators.

Single column tables that merely serve to prove the existence of a
concept are valid if those concepts are part of your data model (who
are my customers?) but not if they are part of the intrinsics that you
base your data model on (these are the colors existing in the physical
world). The question is where you draw the line. PostgreSQL gives you
a default line. In don't think you can operate completely without any
line.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Chris Travers 2005-07-27 20:13:26 MySQL to PostgreSQL, was ENUM type
Previous Message Josh Berkus 2005-07-27 17:51:21 Re: ENUM type

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew - Supernews 2005-07-27 18:21:07 Re: RESULT_OID Bug
Previous Message Josh Berkus 2005-07-27 17:51:21 Re: ENUM type