| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org,Melvin Davidson <melvin6925(at)gmail(dot)com>,Thomas Poty <thomas(dot)poty(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Array of foreign key |
| Date: | 2017-12-22 21:05:18 |
| Message-ID: | B4846243-6401-4BF0-828C-BB3906DA423C@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Finzel | 2017-12-22 21:15:21 | Problem with pgq3 packages missing pgq_node |
| Previous Message | Melvin Davidson | 2017-12-22 20:56:35 | Re: Array of foreign key |