EAV or not to EAV?

From: Reg Me Please <regmeplease(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: EAV or not to EAV?
Date: 2007-11-22 08:48:35
Message-ID: 200711220948.36142.regmeplease@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

Hi all.

I have to take into account the update history of every single
field into a number of tables.
Those updates can come to the future (next values) but also to the
past (history fix) and apply only to some fields, usually not to the
entire record.
Every lookup in those tables is always related to a timestamp that
normally is the current timestamp, but can also be a past timestamp.

I've come up with a "traditionally regretted" EAV design with the add of
timestamps for the history. And the related problems, some of which have
been solved by Joe Conways's crosstab contrib.

Is there a better idea than mine? I hope so.

--
Reg me Please
<Non quietis maribus nauta>

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Oleg Bartunov 2007-11-22 10:57:34 Re: EAV or not to EAV?
Previous Message porntipa 2007-11-22 04:57:10 How to install Postgresql 8.3.x on windows XP

Browse pgsql-general by date

  From Date Subject
Next Message Devrim GÜNDÜZ 2007-11-22 08:55:29 Re: POLL: Women-sized t-shirts for PostgreSQL
Previous Message Ottavio Campana 2007-11-22 08:14:09 Re: Read-only availability of a standby server?