From: | Jasen Betts <jasen(at)xnet(dot)co(dot)nz> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Type inheritance |
Date: | 2009-06-06 12:04:40 |
Message-ID: | h0dm0o$h6b$1@reversiblemaps.ath.cx |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On 2009-06-06, Gianvito Pio <pio(dot)gianvito(at)gmail(dot)com> wrote:
> --001485f44bfe3e357c046ba8b3d6
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 7bit
>
> Oh that was just an example...Let me make a real example:
> I have a table "Sensors" (that has to contain different sensor types) with
> a Value. That value doesn't have to be fixed, but I want to define it in a
> way that it changes its structure when the sensor type changes. For
> example, for Temperature sensor I would like to have just a float number,
> but for the humidity I could need of absolute and relative humidity
> (2 floats). I'd just like to know if I can say that the VALUE is a composite
> type...that I have then to specialize in Temp Type and Humidity type...using
> them in their particular case.
this appears to be EAV in disguise.
From | Date | Subject | |
---|---|---|---|
Next Message | Gianvito Pio | 2009-06-06 14:18:57 | Re: Type inheritance |
Previous Message | Gianvito Pio | 2009-06-06 07:10:12 | Re: Type inheritance |