Re: Migrating a MySQL schema with an enum

From: "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>
To: Mart?n Marqu?s <martin(at)bugs(dot)unl(dot)edu(dot)ar>, Vincent Stoessel <vincent(at)xaymaca(dot)com>
Cc: SQL <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Migrating a MySQL schema with an enum
Date: 2002-03-21 16:02:28
Message-ID: 20020321160227.GC9471@rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

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)
>
> <snip>
>
> 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

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message GRIMOIS Eric 2002-03-21 17:21:50 Sequence not updated after a copy ?
Previous Message Vincent Stoessel 2002-03-21 14:40:42 Re: Migrating a MySQL schema with an enum