>Please DO NOT use EMUMs. That is old. They are hard to maintain. I also
>know from experience that MySql does not check
>integrity of enums. It's possible you can have data in a MySql table
>column
>that is not valid for current enum constraint on that column.
>EG: When porting, the enum for a columm (VALID) was "yes, no", but I
>found
>a few that had "maybe" as data.
>
>The way to go is to simply implement FOREIGN KEYs. Much easier to
>maintain
>in PostgreSQL.
Full ack.
Andreas
--
2ndQuadrant - The PostgreSQL Support Company
