On Tue, Mar 8, 2011 at 11:41 PM, John R Pierce <pie...@hogranch.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 -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general