X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6FADD52801 for ; Tue, 28 Jun 2005 16:50:08 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 29379-10 for ; Tue, 28 Jun 2005 19:50:00 +0000 (GMT) Received: from linda-5.paradise.net.nz (bm-5a.paradise.net.nz [202.0.58.24]) by svr1.postgresql.org (Postfix) with ESMTP id 8095F529E3 for ; Tue, 28 Jun 2005 16:49:57 -0300 (ADT) Received: from smtp-1.paradise.net.nz (smtp-1b.paradise.net.nz [202.0.32.210]) by linda-5.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IIT0096I8FA3C@linda-5.paradise.net.nz> for pgsql-sql@postgresql.org; Wed, 29 Jun 2005 07:49:58 +1200 (NZST) Received: from [192.168.1.50] (203-79-75-147.paradise.net.nz [203.79.75.147]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id EB3B482B77 for ; Wed, 29 Jun 2005 07:49:57 +1200 (NZST) Date: Wed, 29 Jun 2005 07:55:23 +1200 From: Nick Johnson Subject: Re: ENUM like data type In-reply-to: <200506281522.25124.martin@bugs.unl.edu.ar> To: pgsql-sql@postgresql.org Message-id: <42C1AB2B.1020503@notdot.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-15; format=flowed Content-transfer-encoding: 8BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) References: <11bgc1oblfasq3d@corp.supernews.com> <200506281522.25124.martin@bugs.unl.edu.ar> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.229 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200506/344 X-Sequence-Number: 21945 Martín Marqués wrote: > >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. > > You mean like all those instances in the PostgreSQL system catalogs where character(1) has been used as a pseudo-enum of sorts? -Nick Johnson