From: =?iso-8859-15?q?Mart=EDn_Marqu=E9s?= <martin@bugs.unl.edu.ar>
To: PFC <lists@boutiquenumerique.com>
Subject: Re: ENUM like data type
Date: Tue, 28 Jun 2005 15:22:25 -0300
User-Agent: KMail/1.7.1
Cc: "Mike Rylander" <mrylander@gmail.com>, pgsql-sql@postgresql.org
References: <11bgc1oblfasq3d@corp.supernews.com>
	<b918cf3d050628042253044ba@mail.gmail.com>
	<op.ss3aruu5th1vuj@localhost>
In-Reply-To: <op.ss3aruu5th1vuj@localhost>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200506281522.25124.martin@bugs.unl.edu.ar>
MailScanner: Found to be clean

El Mar 28 Jun 2005 13:58, PFC escribi=F3:
>=20
> >> Here is where I get uncertain as to if this is possible. My idea is to
> >> create a pseudo type that triggers the creation of it's lookup tables
> >> the same way the SERIAL type triggers creation of a sequence and retur=
ns
> >> an int with the right default value.
>=20
> 	Personnally I use one table which has columns (domain, name) and which =
=20
> stores all enum values for all different enums.
> 	I have then CHECK( is_in_domain( column, 'domain_name' )) which is a =20
> simple function which checks existence of the value in this domain (SELEC=
T =20
> 1 FROM domains WHERE domain=3D$2 AND name=3D$1 LIMIT 1) for instance.
> 	You can also use integers.

I personally think that the ENUM data type is for databases that are not we=
ll=20
designed. So, if you see the need for ENUM, that means you need to re-think=
=20
your data design.

=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--------------------------------------------------------