Re: equivalent of mysql's SET type? - Mailing list pgsql-general

From Reece Hart
Subject Re: equivalent of mysql's SET type?
Date
Msg-id AANLkTinWeoBE+dnNxTWqqw0KA+ksRQo2P5hZ6PK7x43F@mail.gmail.com
Whole thread Raw
In response to Re: equivalent of mysql's SET type?  (Darren Duncan <darren@darrenduncan.net>)
Responses Re: equivalent of mysql's SET type?  (Darren Duncan <darren@darrenduncan.net>)
List pgsql-general
On Tue, Mar 8, 2011 at 5:52 PM, Darren Duncan <darren@darrenduncan.net> wrote:
Try starting with an enum type to define the possible values:

 CREATE TYPE Consequence_Type
   AS ENUM ('ESSENTIAL_SPLICE_SITE','STOP_GAINED',
     'STOP_LOST','COMPLEX_INDEL','SPLICE_SITE');

... and then you could try using "ARRAY OF Consequence_Type" or some such.

Arrays occurred to me, but they don't give a set (i.e., a consequence type can appear more than once) unless I write the code to dedupe the array. However, if I were going to put that much effort into it, I might as well represent the set directly and obviate the dedupe. Or, am I missing something from your suggestion? 

-Reece

pgsql-general by date:

Previous
From: Josh Kupershmidt
Date:
Subject: Re: Using bytea field...
Next
From: Reece Hart
Date:
Subject: Re: equivalent of mysql's SET type?