Re: Type inheritance
От | Jasen Betts |
---|---|
Тема | Re: Type inheritance |
Дата | |
Msg-id | h0dm0o$h6b$1@reversiblemaps.ath.cx обсуждение исходный текст |
Ответ на | Type inheritance (Gianvito Pio <pio.gianvito@gmail.com>) |
Ответы |
Re: Type inheritance
|
Список | pgsql-sql |
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.
В списке pgsql-sql по дате отправления: