From: Reg Me Please <regmeplease@gmail.com>
To: pgsql-general@postgresql.org
Subject: EAV or not to EAV?
Date: Thu, 22 Nov 2007 09:48:35 +0100
Message-ID: <200711220948.36142.regmeplease@gmail.com> (raw)
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>
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-admin@postgresql.org
Cc: regmeplease@gmail.com, pgsql-general@postgresql.org
Subject: Re: EAV or not to EAV?
In-Reply-To: <200711220948.36142.regmeplease@gmail.com>
* 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