Received: from ece.rice.edu (ece.rice.edu [128.42.4.34]) by postgresql.org (Postfix) with ESMTP id 7E7474759ED for ; Thu, 21 Mar 2002 11:02:26 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by ece.rice.edu (Postfix) with ESMTP id 190F068A5F; Thu, 21 Mar 2002 10:02:31 -0600 (CST) Received: from wallace.ece.rice.edu (wallace.ece.rice.edu [128.42.12.154]) by ece.rice.edu (Postfix) with ESMTP id 41D3368A5C; Thu, 21 Mar 2002 10:02:28 -0600 (CST) Received: from reedstrm by wallace.ece.rice.edu with local (Exim 3.34 #1 (Debian)) id 16o51I-0002W9-00; Thu, 21 Mar 2002 10:02:28 -0600 Date: Thu, 21 Mar 2002 10:02:28 -0600 From: "Ross J. Reedstrom" To: Mart?n Marqu?s , Vincent Stoessel Cc: SQL Subject: Re: Migrating a MySQL schema with an enum Message-ID: <20020321160227.GC9471@rice.edu> Mail-Followup-To: "Ross J. Reedstrom" , Mart?n Marqu?s , Vincent Stoessel , SQL References: <3C991E29.C90559F4@heart.com.au> <20020321113145.E84DBFA1D@bugs.unl.edu.ar> <3C99F0EA.2050206@xaymaca.com> <3C991E29.C90559F4@heart.com.au> <20020321113145.E84DBFA1D@bugs.unl.edu.ar> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C99F0EA.2050206@xaymaca.com> <20020321113145.E84DBFA1D@bugs.unl.edu.ar> User-Agent: Mutt/1.3.27i X-Virus-Scanned: by AMaViS snapshot-20010714 X-Archive-Number: 200203/279 X-Sequence-Number: 7158 On Thu, Mar 21, 2002 at 09:40:42AM -0500, Vincent Stoessel wrote: > Mart?n Marqu?s wrote: > >On Mi? 20 Mar 2002 20:41, you wrote: > > > >>SQL gurus, > >> > >>Migrating a MySQL schema with an enum to PostgreSQL, > >>is there an equivalent type or do I have to declare > >>another table for "enum" values. > > > > > >I had to migrate a DB from MySQL to PostgreSQL that had some enum as field > >data type (I can't believe that something like that exists) > > > > another shot at the mysql db. > Please don't forget that PG also has non standard data types > available. Your pique at seeing what you took as an unfair shot at another db caused you to be blinded to what Martin was pointing out. In this case, MySQL has a gratutiously non-standard feature: the equivalent CHECK constraint is only a few more characters, and easier to read (IMHO) Ross