From: =?iso-8859-15?q?Mart=EDn_Marqu=E9s?= <martin@bugs.unl.edu.ar>
To: pgsql-sql@postgresql.org
Subject: Re: ENUM like data type
Date: Wed, 29 Jun 2005 10:21:10 -0300
User-Agent: KMail/1.7.1
References: <ED4E30DD9C43D5118DFB00508BBBA76EB167AF@neptun.sonorys.at>
In-Reply-To: <ED4E30DD9C43D5118DFB00508BBBA76EB167AF@neptun.sonorys.at>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200506291021.10986.martin@bugs.unl.edu.ar>
MailScanner: Found to be clean

El Mi=E9 29 Jun 2005 09:40, K=D6PFERL Robert escribi=F3:
>=20
> |
> |I personally think that the ENUM data type is for databases=20
> |that are not well=20
> |designed. So, if you see the need for ENUM, that means you=20
> |need to re-think=20
> |your data design.
> |
>=20
> I disagree. In several relations (views of the world) one needs to have a
> hand full of well defined values while
> integers or bools are not appropriate and strings are too free form.
> For example male female or true and false. Whilst the second has a well
> known type, other things like a telephone number type don't have such typ=
e.
> So a new one should be created instead of (varchar/ xy between 4 and 8). =
One
> might argue that new 1:n relations with integrity shall be established but
> this is in my eyes overkill for a constant number of values.
> Also think of schema export without data. These values are part of the
> schema data but not the schema itself which in this sense is wrong

Please, most of this can be done with CHECK(...).

=2D-=20
select 'mmarques' || '@' || 'unl.edu.ar' AS email;
=2D--------------------------------------------------------
Mart=EDn Marqu=E9s          |   Programador, DBA
Centro de Telem=E1tica	|     Administrador
               Universidad Nacional
                    del Litoral
=2D--------------------------------------------------------