From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Martín Marqués <martin@bugs.unl.edu.ar>
Cc: PFC <lists@boutiquenumerique.com>
Cc: Mike Rylander <mrylander@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: ENUM like data type
Date: Tue, 28 Jun 2005 13:46:18 -0500
Message-ID: <1119984378.8208.114.camel@state.g2switchworks.com> (raw)
In-Reply-To: <200506281522.25124.martin@bugs.unl.edu.ar>
References: <11bgc1oblfasq3d@corp.supernews.com>
<b918cf3d050628042253044ba@mail.gmail.com>
<op.ss3aruu5th1vuj@localhost>
<200506281522.25124.martin@bugs.unl.edu.ar>
On Tue, 2005-06-28 at 13:22, Martín Marqués wrote:
> El Mar 28 Jun 2005 13:58, PFC escribió:
> >
> > >> 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 returns
> > >> an int with the right default value.
> >
> > Personnally I use one table which has columns (domain, name) and which
> > stores all enum values for all different enums.
> > I have then CHECK( is_in_domain( column, 'domain_name' )) which is a
> > simple function which checks existence of the value in this domain (SELECT
> > 1 FROM domains WHERE domain=$2 AND name=$1 LIMIT 1) for instance.
> > You can also use integers.
>
> I personally think that the ENUM data type is for databases that are not well
> designed. So, if you see the need for ENUM, that means you need to re-think
> your data design.
I would generally agree, however, a pseudo type like serial that created
the properly fk'd table with all the options in it would be quite nice
to have.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: smarlowe@g2switchworks.com, martin@bugs.unl.edu.ar, lists@boutiquenumerique.com, mrylander@gmail.com
Subject: Re: ENUM like data type
In-Reply-To: <1119984378.8208.114.camel@state.g2switchworks.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox