Re: ENUM like data type

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: Martín Marqués <martin(at)bugs(dot)unl(dot)edu(dot)ar>
Cc: PFC <lists(at)boutiquenumerique(dot)com>, Mike Rylander <mrylander(at)gmail(dot)com>, pgsql-sql(at)postgresql(dot)org
Subject: Re: ENUM like data type
Date: 2005-06-28 18:46:18
Message-ID: 1119984378.8208.114.camel@state.g2switchworks.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql

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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2005-06-28 18:46:39 Re: Occupied port warning
Previous Message Stephen Frost 2005-06-28 18:45:06 Re: [PATCHES] Users/Groups -> Roles

Browse pgsql-sql by date

  From Date Subject
Next Message Nick Johnson 2005-06-28 19:55:23 Re: ENUM like data type
Previous Message Martín Marqués 2005-06-28 18:22:25 Re: ENUM like data type