From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: equivalent of mysql's SET type? |
Date: | 2011-03-09 15:13:31 |
Message-ID: | AANLkTinhFHA+a+5bVY1vbP7yyvnZNYXOSaxCS0vYgrj3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Mar 8, 2011 at 11:41 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 03/08/11 5:06 PM, Reece Hart wrote:
>>
>> I'm considering porting a MySQL database to PostgreSQL. That database uses
>> MySQL's SET type. Does anyone have advice about representing this type in
>> PostgreSQL?
>>
>> MySQL DDL excerpt:
>> CREATE TABLE `transcript_variation` (
>> `transcript_variation_id` int(10) unsigned NOT NULL AUTO_INCREMENT,
>> `transcript_stable_id` varchar(128) NOT NULL,
>> ...
>> `consequence_type`
>> set('ESSENTIAL_SPLICE_SITE','STOP_GAINED','STOP_LOST','COMPLEX_INDEL','SPLICE_SITE')
>> ) ENGINE=MyISAM AUTO_INCREMENT=174923212 DEFAULT CHARSET=latin1;
>>
>>
>
> why not just have a set of booleans in the table for these individual on/off
> attributes? wouldn't that be simplest?
+1
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2011-03-09 15:27:48 | Re: [GENERAL] FW: backup using pg_dump postgreSQL 8.3.8 |
Previous Message | David Johnston | 2011-03-09 15:02:50 | Re: Copying data from one table to another - how to specify fields? |