EAV or not to EAV? - Mailing list pgsql-general

From Reg Me Please
Subject EAV or not to EAV?
Date
Msg-id 200711220948.36142.regmeplease@gmail.com
Whole thread Raw
Responses Re: EAV or not to EAV?
Re: EAV or not to EAV?
List 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>

pgsql-general by date:

Previous
From: Ottavio Campana
Date:
Subject: Re: Read-only availability of a standby server?
Next
From: Devrim GÜNDÜZ
Date:
Subject: Re: POLL: Women-sized t-shirts for PostgreSQL