From: Jasen Betts <jasen@xnet.co.nz>
To: pgsql-sql@postgresql.org
Subject: Re: Type inheritance
Date: 6 Jun 2009 12:04:40 GMT
Message-ID: <h0dm0o$h6b$1@reversiblemaps.ath.cx> (raw)
References: <5eca56860906050330w6171b327k95881b13c4dca466@mail.gmail.com>
<4A294A00.5020802@gmail.com>
<5eca56860906060010y4177b88apcf587d62f7286b5d@mail.gmail.com>
On 2009-06-06, Gianvito Pio <pio.gianvito@gmail.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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: jasen@xnet.co.nz
Subject: Re: Type inheritance
In-Reply-To: <h0dm0o$h6b$1@reversiblemaps.ath.cx>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox