| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Vernon Smith <vwu98034(at)lycos(dot)com> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Inheritance & multiple-value fields |
| Date: | 2003-08-04 15:49:58 |
| Message-ID: | Pine.LNX.4.33.0308040947070.10328-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, 2 Aug 2003, Vernon Smith wrote:
>
> We usually use another table for a multi-valued field. Is possible
> having a single multi-valued field table for all tables in the same
> heredity, other than having a multi-valued table for every single
> tables in the heredity?
The SQL 3 standard has an enumerated type listed in it, but I don't think
it's likely to show up in Postgresql any time soon. you can approximate
these using a check in() constraint.
Or are you looking at more than one value in the same field? In that
case, arrays are a way to do that.
both enumerated types and arrays break the strict relational model, but
sometimes they're the simpler, cleaner soltution.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Freddy Menjívar M. | 2003-08-04 15:52:19 | Functions and procedures code!!!! |
| Previous Message | Joe Conway | 2003-08-04 15:46:58 | Re: plPHP -- sort of an announcement.. but not commercial |